path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
path-to-regexp
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| path-to-regexp npm |
|
|
path-to-regexp
| Product | Affected | Fixed in |
|---|---|---|
| path-to-regexp npm |
|
|
0.1.108.0.03.3.06.3.0Impact:
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.
From the CVE record · openjs
path-to-regexp can generate a regular expression that backtracks catastrophically when a route segment has three or more parameters separated by characters other than periods. An attacker who can supply a matching path may trigger excessive processing. The input does not specify whether authentication or user interaction is required.
Check applications using npm path-to-regexp in the reported affected ranges: <0.1.13, >=0.2.0 <1.9.0, >=7.0.0 <8.0.0, >=2.0.0 <3.3.0, or >=4.0.0 <6.3.0.