Skip to content

[Snyk] Security upgrade path-to-regexp from 6.2.2 to 8.0.0#968

Closed
cdimascio wants to merge 1 commit intomasterfrom
snyk-fix-334382a0fda3f07bd7ff5664af73a871
Closed

[Snyk] Security upgrade path-to-regexp from 6.2.2 to 8.0.0#968
cdimascio wants to merge 1 commit intomasterfrom
snyk-fix-334382a0fda3f07bd7ff5664af73a871

Conversation

@cdimascio
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 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
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
  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:

🦉 Regular Expression Denial of Service (ReDoS)

Copy link
Copy Markdown
Contributor

@cvchauhan cvchauhan left a comment

Choose a reason for hiding this comment

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

looks like there is change in latest package you need to update openapi.metadata.ts pathToRegexp functions

@cvchauhan
Copy link
Copy Markdown
Contributor

Pr has been raised already
#975

@cdimascio
Copy link
Copy Markdown
Owner Author

closing in favor of #976

@cdimascio cdimascio closed this Sep 15, 2024
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.

3 participants