[Snyk] Security upgrade axios from 1.4.0 to 1.18.0#66
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-AXIOS-18065351 - https://snyk.io/vuln/SNYK-JS-AXIOS-18060659 - https://snyk.io/vuln/SNYK-JS-AXIOS-18060730 - https://snyk.io/vuln/SNYK-JS-AXIOS-18065349 - https://snyk.io/vuln/SNYK-JS-AXIOS-18060165 - https://snyk.io/vuln/SNYK-JS-AXIOS-18060167 - https://snyk.io/vuln/SNYK-JS-AXIOS-18065355
|
This is a minor version upgrade for axios from 1.4.0 to 1.18.0. While it does not contain major API breaking changes, it introduces several behavioral modifications due to significant security hardening across multiple releases. Verification is recommended. Key Changes:
Recommendation: Review your application's usage of axios, particularly if it involves complex redirects, proxy configurations, or relies on lenient URL parsing. It is important to test after upgrading to ensure these security enhancements do not unexpectedly break functionality. Source: GitHub Releases
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Snyk has created this PR to fix 7 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
package.jsonyarn.lockNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-AXIOS-18065351
SNYK-JS-AXIOS-18060659
SNYK-JS-AXIOS-18060730
SNYK-JS-AXIOS-18065349
SNYK-JS-AXIOS-18060165
SNYK-JS-AXIOS-18060167
SNYK-JS-AXIOS-18065355
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncontrolled Recursion
🦉 Prototype Pollution