[Snyk] Security upgrade axios from 1.5.0 to 1.12.0

[codingdud]

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

Snyk changed the following file(s):

• loginnext/package.json
• loginnext/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-12613773	738

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
just-login	Error			Sep 18, 2025 9:12am
loginapi	Ready	Preview	Comment	Sep 18, 2025 9:12am

[gemini-code-assist]

Summary of Changes

Hello @codingdud, 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 automates a crucial security update by upgrading the axios package to version 1.12.0. This change is essential for mitigating a high-severity vulnerability related to resource allocation, thereby enhancing the overall security posture of the project by ensuring all dependencies are up-to-date and secure.

Highlights

• Security Upgrade: The axios package has been upgraded from version 1.5.0 to 1.12.0 to address a critical security vulnerability.
• Vulnerability Fixed: This upgrade specifically resolves the "Allocation of Resources Without Limits or Throttling" vulnerability (SNYK-JS-AXIOS-12613773), which had a score of 738.
• Dependency Updates: Both package.json and package-lock.json have been updated to reflect the new axios version and its transitive dependencies, ensuring a secure and consistent dependency tree.

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, automatically generated by Snyk, upgrades axios from version 1.5.0 to 1.12.0. This is an important security update to address the 'Allocation of Resources Without Limits or Throttling' vulnerability (SNYK-JS-AXIOS-12613773). While the dependency upgrade is the correct first step, it may not be sufficient on its own. To fully resolve the vulnerability, you should also configure axios to set limits on request and response data sizes. I've added a specific comment on how to achieve this. The changes in package-lock.json are consistent with the axios upgrade.

[gemini-code-assist]

While upgrading axios is a crucial step to address the security vulnerability SNYK-JS-AXIOS-12613773, it's important to take further action to fully mitigate the 'Allocation of Resources Without Limits or Throttling' issue. I recommend explicitly setting limits on both the request body and response body size in your axios instances.

For example, in loginnext/src/api/axios.js, you can add maxBodyLength and maxContentLength to your axios.create configurations:

const SAFE_PAYLOAD_LIMIT = 10 * 1024 * 1024; // 10MB limit, adjust as needed

export default axios.create({
    baseURL: BASE_URL,
    headers:{
        "Access-Control-Allow-Origin": true
    },
    maxContentLength: SAFE_PAYLOAD_LIMIT,
    maxBodyLength: SAFE_PAYLOAD_LIMIT
});

export const axiosPrivate = axios.create({
    baseURL: BASE_URL,
    headers: { 'Content-Type': 'application/json' },
    withCredentials: true,
    maxContentLength: SAFE_PAYLOAD_LIMIT,
    maxBodyLength: SAFE_PAYLOAD_LIMIT
});

This will prevent potential Denial of Service (DoS) attacks where a malicious client or server could send an extremely large payload. Please adjust the limit according to your application's needs.