-
Notifications
You must be signed in to change notification settings - Fork 48
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
Version bump path-to-regexp #204
Comments
Hi, feel free to open a PR. This repo is in maintenance mode and we recommend using unleash-edge instead. |
@gastonfournier can you add me as a contributor so I open a PR? I tried to push a branch but its not working. |
Hi @spirrello, usually you have to fork the repo and from your fork you can open a PR. Here's a detailed explanation of how to do it: https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project |
@gastonfournier Thx, I've opened #205. |
Describe the bug
Hello,
The
path-to-regexp
is currently affected byCVE-2024-52798
and is listed as a high vulnerability. Could you please consider bumping the version to a newer release that is not affected? Our container image scanning is picking this up and it would be great to get this resolved so we can continue using the proxy.Link to the vulnerability details: https://nvd.nist.gov/vuln/detail/CVE-2024-52798
Steps to reproduce the bug
Run any vulnerability scan on this repo and it will pick up the CVE.
Expected behavior
Zero vulnerabilities listed as
high
.Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
1.4.8
Subscription type
None
Hosting type
None
SDK information (language and version)
No response
The text was updated successfully, but these errors were encountered: