Back to feed
EUVD-2024-3506 · Published Dec 5, 2024
path-to-regexp contains a ReDoS
Impact
The regular expression that is vulnerable to backtracking can be generated in versions before 0.1.12 of path-to-regexp, originally reported in CVE-2024-45296
Patches
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
Technologies
Path-To-Regexp Path-To-Regexp
Weaknesses
CWE-1333
CVSS scores
- v3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK
InferredWhere this vulnerability fits in an attack
Initial Access
References
- https://github.com/pillarjs/path-to-regexp/commit/f01c26a013b1889f0c217c643964513acf17f6a4
- https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w
- https://security.netapp.com/advisory/ntap-20250124-0002/
- https://nvd.nist.gov/vuln/detail/CVE-2024-52798
- https://blakeembrey.com/posts/2024-09-web-redos
- https://github.com/pillarjs/path-to-regexp
Potentially impacted assets
See if this affects your attack surface
