GHSA-rhx6-c78j-4q9w
Suggest an improvement- Source
- https://github.com/advisories/GHSA-rhx6-c78j-4q9w
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/12/GHSA-rhx6-c78j-4q9w/GHSA-rhx6-c78j-4q9w.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-rhx6-c78j-4q9w
- Aliases
- Related
- Published
- 2024-12-05T22:40:47Z
- Modified
- 2024-12-06T00:33:27Z
- Summary
- Unpatched `path-to-regexp` ReDoS in 0.1.x
- Details
-
Impact
The regular expression that is vulnerable to backtracking can be generated in the 0.1.x release of
path-to-regexp, originally reported in CVE-2024-45296Patches
Upgrade to 0.1.12.
Workarounds
Avoid using two parameters within a single path segment, when the separator is not
.(e.g. no/:a-:b). Alternatively, you can define the regex used for both parameters and ensure they do not overlap to allow backtracking.References
- https://github.com/advisories/GHSA-9wv6-86v2-598j
- https://blakeembrey.com/posts/2024-09-web-redos/
- Database specific
{ "nvd_published_at": "2024-12-05T23:15:06Z", "cwe_ids": [ "CWE-1333" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-12-05T22:40:47Z" }- References
-
- https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w
- https://nvd.nist.gov/vuln/detail/CVE-2024-52798
- https://github.com/pillarjs/path-to-regexp/commit/f01c26a013b1889f0c217c643964513acf17f6a4
- https://blakeembrey.com/posts/2024-09-web-redos
- https://github.com/pillarjs/path-to-regexp
Affected packages
npm / path-to-regexp
Package
- Name
- path-to-regexp
- View open source insights on deps.dev
- Purl
- pkg:npm/path-to-regexp