[Snyk] Security upgrade axios from 0.27.2 to 1.13.5

[q1blue]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• mage_ai/frontend/package.json
• mage_ai/frontend/yarn.lock

Note 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 run yarn to update the contents of the ./yarn/cache directory.
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:

	Issue	Score
	Prototype Pollution SNYK-JS-AXIOS-15252993	225

---

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

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs an essential security upgrade for the axios package in the frontend dependencies. It addresses a high-severity Prototype Pollution vulnerability by updating axios to a secure version, ensuring the project's frontend remains protected against known exploits. The update also includes necessary adjustments to the dependency lock file to reflect the new package versions and their transitive dependencies.

Highlights

• Security Upgrade: Upgraded the axios package from version 0.27.2 to 1.13.5 in the frontend dependencies.
• Vulnerability Fix: Addressed a high-severity 'Prototype Pollution' vulnerability (SNYK-JS-AXIOS-15252993) by updating axios to a secure version.
• Dependency Updates: Updated yarn.lock to reflect the new axios version and its updated transitive dependencies, including follow-redirects, form-data, and several newly introduced packages.

Changelog

• mage_ai/frontend/package.json
  • Updated axios dependency version from ^0.27.2 to ^1.13.5.
• mage_ai/frontend/yarn.lock
  • Updated axios package entry to version 1.13.5.
  • Updated follow-redirects dependency from 1.15.6 to 1.15.11.
  • Updated form-data dependency from 4.0.0 to 4.0.5.
  • Added proxy-from-env as a new direct dependency for axios.
  • Introduced new transitive dependencies: call-bind-apply-helpers, dunder-proto, es-define-property, es-object-atoms, es-set-tostringtag, get-intrinsic, get-proto, gopd, has-symbols, and math-intrinsics.

Activity

• Snyk automatically created this pull request to fix identified vulnerabilities in the project's yarn dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades axios from version 0.27.2 to 1.13.5 to fix a security vulnerability. This is a major version upgrade and introduces breaking changes. While the dependency update itself is correct, the consuming code needs to be audited to ensure compatibility. I've identified a couple of potential issues in the error handling logic that could be exacerbated by this upgrade and a leftover debug alert that should be removed. Please see my detailed comment on package.json.

[gemini-code-assist]

Upgrading axios to a new major version (0.x to 1.x) introduces significant breaking changes. It's crucial to audit the codebase for compatibility. I've found a few areas of concern:

1. Inconsistent Error Handling: In mage_ai/frontend/api/utils/fetcher.ts, the .catch block for axios requests has logic that creates inconsistent error objects:

   .catch(error => {
     reject({
       ...(error?.response || error),
     });
   });

   This can lead to unpredictable behavior in error handlers downstream. With axios v1, the AxiosError object structure has been refined. It's recommended to reject the original error object to maintain consistency and access to all error properties, like so: reject(error).

2. Debugging alert: In mage_ai/frontend/api/useMutate.ts, there is a debugging alert in an onError handler:

   onError: (error: any, ...) => {
     alert(`${JSON.stringify(error)}`);
     // ...
   },

   This should be removed as it provides a poor user experience and could potentially leak sensitive information in production.

I recommend addressing these points to ensure the application remains stable after this important security upgrade.