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-dev] Upgrade express from 4.12.4 to 4.21.0 #138

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

Conversation

ramy-abbas
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade express from 4.12.4 to 4.21.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 31 versions ahead of your current version.

  • The recommended version was released on 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
npm:fresh:20170908
738 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
738 Proof of Concept
medium severity Open Redirect
SNYK-JS-EXPRESS-6474509
738 No Known Exploit
medium severity Cross-site Scripting
SNYK-JS-EXPRESS-7926867
738 No Known Exploit
low severity Cross-site Scripting
SNYK-JS-SEND-7926862
738 No Known Exploit
low severity Cross-site Scripting
SNYK-JS-SERVESTATIC-7926865
738 No Known Exploit
Release notes
Package name: express from express GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

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