[Snyk] Fix for 2 vulnerabilities

[saurabharch]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Validation of Specified Type of Input SNYK-JS-VALIDATOR-13395830	658
	SQL Injection SNYK-JS-TYPEORM-13746469	648

---

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:

🦉 SQL Injection

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, 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, aims to enhance the project's security posture by resolving two identified medium-severity vulnerabilities. The changes involve updating core npm dependencies, specifically class-validator and typeorm, to their latest secure versions, which in turn updates a multitude of their transitive dependencies to ensure a more robust and secure application environment.

Highlights

• Security Vulnerability Fixes: This pull request addresses two medium-severity security vulnerabilities identified by Snyk in the project's npm dependencies.
• Dependency Upgrades: The class-validator package has been updated from version 0.9.1 to 0.13.0, and the typeorm package has been upgraded from 0.2.12 to 0.3.26.
• Vulnerabilities Addressed: The specific vulnerabilities fixed are 'Improper Validation of Specified Type of Input' (SNYK-JS-VALIDATOR-13395830) and 'SQL Injection' (SNYK-JS-TYPEORM-13746469).

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 class-validator and typeorm to resolve two security vulnerabilities. While necessary, the upgrade to typeorm v0.3.x introduces significant breaking changes. The BaseEntity.findOne(id) method is no longer supported, which will cause runtime errors in ChangePassword.ts and Me.ts. I have left a critical comment on the package.json file detailing the required code modifications to ensure the application remains functional after this dependency upgrade. Please address these issues before merging.

[gemini-code-assist]

The upgrade of typeorm to version 0.3.x is a major update with breaking changes. The BaseEntity.findOne(id) method, which was used to find an entity by its primary key, has been removed.

This will cause runtime errors in the following files:

1. src/modules/user/ChangePassword.ts on line 26:

   const user = await User.findOne(userId);

   The userId is a string from Redis. This should be updated to:

   const user = await User.findOneBy({ id: parseInt(userId, 10) });

2. src/modules/user/Me.ts on line 14:

   return User.findOne(ctx.req.session!.userId);

   This should be updated to:

   return User.findOneBy({ id: ctx.req.session!.userId });

These changes are required to make the application work with the new version of typeorm. Please apply these fixes in a follow-up commit to this PR.