[Snyk] Security upgrade axios from 1.12.2 to 1.20.0

[winjer]

Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-AXIOS-20244996	738
	Prototype Pollution SNYK-JS-AXIOS-20245050	738
	Improper Input Validation SNYK-JS-AXIOS-20245058	738
	Prototype Pollution SNYK-JS-AXIOS-20245064	738

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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:

🦉 Prototype Pollution
🦉 Improper Input Validation

[winjer]

This upgrade spans multiple minor versions and includes several security hardening fixes and behavioral changes that require verification.

Key Changes:

• Behavioral Changes (v1.18.0):
  • The fetch adapter now enforces maxBodyLength and maxContentLength, which could cause previously successful large requests to fail. [2]
  • Proxy requests now preserve user-supplied Host headers, which may affect applications relying on the previous behavior. [2]
  • URL protocol parsing is now stricter and requires a colon. [2]
• Security Hardening: Multiple versions within this range (v1.13.0 - v1.20.0) introduce fixes for prototype pollution, redirect handling, and configuration merging. [1, 2] These security improvements can change how Axios handles edge-case configurations and malformed inputs.
• Deprecations (v1.20.0): New RFC 9110 compliant HTTP status names have been added (e.g., ContentTooLarge). The older aliases (PayloadTooLarge) are retained for backward compatibility but are now deprecated. [1]

Recommendation: While no mandatory API refactoring is required, it is important to verify application behavior related to large request bodies (if using the fetch adapter), proxy usage, and any reliance on previously lenient URL or configuration parsing. Testing is recommended to ensure the security hardening does not introduce unexpected side effects.

Source: GitHub Releases

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.