[Snyk] Security upgrade axios from 1.16.1 to 1.18.0

[crew-security]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-AXIOS-18060730	738
	Prototype Pollution SNYK-JS-AXIOS-18065351	738
	Permissive List of Allowed Inputs SNYK-JS-AXIOS-18065357	738
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060165	708
	Uncontrolled Recursion SNYK-JS-AXIOS-18060167	708
	Prototype Pollution SNYK-JS-AXIOS-18060659	708
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060804	708
	Prototype Pollution SNYK-JS-AXIOS-18065349	708
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18065353	708
	Prototype Pollution SNYK-JS-AXIOS-18065355	708

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncontrolled Recursion
🦉 Prototype Pollution

[crew-security]

This upgrade from version 1.16.1 to 1.18.0 includes security hardening and behavioral changes that require verification.

Key Changes in v1.18.0:

• Stricter URL Validation: Requests with malformed http: or https: URLs that are missing the // prefix will now be rejected with an ERR_INVALID_URL error.
• Redirect Header Safety (Node.js): To prevent security leaks, sensitive headers (like custom authorization tokens) are now automatically stripped during cross-origin redirects. Applications relying on passing such headers to a different origin will need to be reviewed.

Key Changes in v1.17.0:

• Authentication Handling: The behavior for handling Basic authentication during redirects in Node.js was changed to be more secure, restoring it for same-origin redirects but continuing to strip credentials for cross-origin redirects.

Recommendation: These changes are primarily for security and correctness. However, because they alter previous behaviors, there is a moderate risk of impacting applications that relied on the older, less strict functionality. It is recommended to verify that URL formatting is correct and to test any functionality involving cross-origin redirects with authentication headers.

Source: Axios v1.x CHANGELOG

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