[Snyk] Fix for 4 vulnerabilities

[iamdrewfortini]

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

Snyk changed the following file(s):

• apps/backend/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	149
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15105315	149
	Directory Traversal SNYK-JS-TAR-15032660	149
	Directory Traversal SNYK-JS-TAR-15127355	129

---

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
🦉 Directory Traversal

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, 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, automatically generated by Snyk, focuses on enhancing the security posture of the apps/backend service by upgrading critical dependencies. The changes aim to resolve multiple identified vulnerabilities, ensuring the application benefits from the latest security patches and improvements provided by updated package versions.

Highlights

• Security Vulnerability Resolution: This PR addresses four identified security vulnerabilities, including two high-severity "Allocation of Resources Without Limits or Throttling" issues and two medium-severity "Directory Traversal" issues, as detected by Snyk.
• Dependency Version Upgrades: Key dependencies bcrypt and next have been upgraded to their latest versions to mitigate the identified vulnerabilities. Specifically, bcrypt was updated from ^5.1.1 to ^6.0.0, and next was updated from 15.4.1 to 16.1.5.

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, aims to fix four security vulnerabilities by upgrading bcrypt and next dependencies. The upgrade of next to a new major version (16.1.5) is appropriate for fixing the listed vulnerabilities. However, the upgrade of bcrypt to version 6.0.0 is concerning, as this version does not appear to exist on the official npm registry, which could indicate an error or a potential security risk. Additionally, a related dependency, @next/bundle-analyzer, has not been updated to match the new version of next, which will likely cause issues. Finally, as noted in the PR description, pnpm-lock.yaml needs to be manually updated. I've added specific comments with suggestions to address these points.

[gemini-code-assist]

The bcrypt package is being updated to version 6.0.0, but this version does not appear to exist on the public npm registry. The latest version of bcrypt is 5.1.1. This could be an error from Snyk or potentially a security risk if it points to a malicious package. Given that the vulnerabilities mentioned in the PR description are related to next and tar, not bcrypt, I recommend reverting this change to avoid any issues.

Suggested change

	"bcrypt": "^6.0.0",
	"bcrypt": "^5.1.1",

[gemini-code-assist]

While next is being upgraded to 16.1.5, the @next/bundle-analyzer package in your dependencies (line 46) is still at version 15.2.3. To ensure compatibility and prevent potential build issues, this package should also be upgraded to a version compatible with Next.js 16. You'll likely need to update it to a ^16.x.x version.