Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade mongoose from 7.0.3 to 7.5.0 #223

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sidhantpanda
Copy link
Owner

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

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 496/1000
Why? Recently disclosed, Has a fix available, CVSS 4.2
Information Exposure
SNYK-JS-MONGODB-5871303
No No Known Exploit

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

Commit messages
Package name: mongoose The new version differs by 250 commits.
  • 20162c6 chore: release 7.5.0
  • 1cd9384 Merge pull request #13796 from Automattic/7.5
  • 419c64d docs: add comment about top-level dollar keys re: #13796 code review comments
  • a92e8e8 Merge branch 'master' into 7.5
  • d9a4bc4 Merge pull request #13793 from Automattic/vkarpov15/gh-13774
  • 29de9c4 Merge pull request #13786 from Automattic/vkarpov15/handle-top-level-dollar-keys
  • 84e79b9 Merge pull request #13787 from Automattic/vkarpov15/gh-13780
  • a9db5ea types: handle Schema.Types.BigInt in schema definition re: #13780
  • 90fc4d2 Merge pull request #13792 from mreouven/patch-1
  • 41e63bd fix(document): avoid double-calling array getters when using `.get('arr.0')`
  • c1d5b76 Merge pull request #13774 from Automattic/vkarpov15/gh-13748
  • 0d956ce test: fix tests
  • f44e169 Update pipelinestage.d.ts
  • 9f1c24c Update pipelinestage.d.ts
  • 7ec92a7 types(schematypes): add missing BigInt SchemaType
  • fe7f80b test: add tests
  • 40146c8 feat: allow top level dollar keys with findOneAndUpdate(), update()
  • fafa5d5 Merge branch 'master' into 7.5
  • e36fc48 docs: fix link
  • 65245a4 style: fix lint
  • 069651e Merge branch 'master' into 7.5
  • 6eeb875 Merge branch 'master' into vkarpov15/gh-13748
  • e12ae3f chore: release 7.4.5
  • 13c2ad0 fix(model): fix merge issue

See the full diff

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-MONGODB-5871303
@@ -35,7 +35,7 @@
"express": "4.18.2",
"joi": "17.9.1",
"js-yaml": "^4.1.0",
"mongoose": "7.0.3",
"mongoose": "7.5.0",
"swagger-ui-express": "4.6.2",
"winston": "3.8.2",
"winston-transport": "4.5.0"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code patch seems to be updating the version of the "mongoose" package used in the project. It is upgrading from version 7.0.3 to version 7.5.0.

Bug risks and improvement suggestions cannot be determined based on this code patch alone, as it only shows a version update in the package.json file.

However, when updating packages, it is generally a good practice to check the release notes or documentation for any potential breaking changes or new features introduced in the newer version. Additionally, it's advisable to thoroughly test the updated version in your application to ensure compatibility and verify that it behaves as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants