path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| path-to-regexp | path-to-regexp | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Path-to-regexp | Path-to-regexp |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-37ch-88jc-xwx2 | path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.527% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pillarjs
Pillarjs path-to-regexp |
|
| CPEs | cpe:2.3:a:pillarjs:path-to-regexp:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Pillarjs
Pillarjs path-to-regexp |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Path-to-regexp
Path-to-regexp path-to-regexp |
|
| Vendors & Products |
Path-to-regexp
Path-to-regexp path-to-regexp |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Impact: A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in path-to-regexp@0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking. Patches: Upgrade to path-to-regexp@0.1.13 Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group. Workarounds: All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b-:c to /:a-:b([^-/]+)-:c([^-/]+). If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length. | |
| Title | path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters | |
| Weaknesses | CWE-1333 | |
| References |
| |
| Metrics |
cvssV3_1
|