[Snyk] Security upgrade axios from 0.21.4 to 1.6.0

[amplience-snyk]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	676/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.1	Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Request Forgery (CSRF)

[ZephSibley]

@easen-amp A customer have flagged this and asked if we plan to remediate it. I'm not sure it's within the threat model of this service but I'm hoping you might be able to include it in the next release.

[B3nCr]

This has also been flagged by our security tooling as an issue.

[ZephSibley]

This has also been flagged by our security tooling as an issue.

Thanks @B3nCr

I've done the analysis and concluded that CSRF issues are outside the threat model for this service as it works with a public, read-only endpoint, and CSRF attacks rely on the availability of state-changing operations. It would be good to clear this from the board but there is no vulnerability in this instance.

[ghost]

@ZephSibley can you see the similar #101 ? It's also CSRF but it's easier to patch since it's just a bump from 0.21.x to 0.28.x, not a 0.x to 1.x major version bump

[simonseddon]

@ZephSibley appreciate that CSRF may not be 100% applicable to Amplience in and of itself, but for Amplience customers it is. We have dependency vulnerability checks in our builds which are currently blocking due to this.

[B3nCr]

@ZephSibley appreciate that CSRF may not be 100% applicable to Amplience in and of itself, but for Amplience customers it is. We have dependency vulnerability checks in our builds which are currently blocking due to this.

Indeed, this was the issue for us too.