Path-to-regexp is a utility that translates Express-style paths into regular expressions, offering developers a straightforward way to match routes in their applications. Versions 0.1.6 and 0.1.7 share core functionality, both sporting the same description: "Express style path to RegExp utility". They utilize mocha and istanbul for development dependencies. and are released under a MIT license, ensuring flexibility in usage.
The key difference lies in their release dates and repository URL. Version 0.1.6 was released on June 19, 2015, while version 0.1.7 followed on July 28, 2015, indicating a newer, potentially improved or patched release. A subtle change in the repository URL also exists. The older 0.1.6 specifies a standard HTTPS URL, while the newer 0.1.7 uses a git+https URL, suggesting a potential update in how the repository is accessed or handled by package managers. For developers, both versions provide the fundamental routing functionality, but choosing 0.1.7 offers the benefit of using the latest release within that minor version range, possibly incorporating bug fixes or minor enhancements. Developers should evaluate if the newer repository URL scheme impacts their specific workflow.
All the vulnerabilities related to the version 0.1.7 of the package
path-to-regexp outputs backtracking regular expressions
A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b.
For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
These versions add backtrack protection when a custom regex pattern is not provided:
They do not protect against vulnerable user supplied capture groups. Protecting against explicit user patterns is out of scope for old versions and not considered a vulnerability.
Version 7.1.0 can enable strict: true and get an error when the regular expression might be bad.
Version 8.0.0 removes the features that can cause a ReDoS.
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 to /:a-:b([^-/]+).
If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length. For example, halving the attack string improves performance by 4x faster.
Using /:a-:b will produce the regular expression /^\/([^\/]+?)-([^\/]+?)\/?$/. This can be exploited by a path such as /a${'-a'.repeat(8_000)}/a. OWASP has a good example of why this occurs, but the TL;DR is the /a at the end ensures this route would never match but due to naive backtracking it will still attempt every combination of the :a-:b on the repeated 8,000 -a.
Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment using Express v4 and 10 concurrent connections, this translated to average latency of ~600ms vs 1ms.
path-to-regexp contains a ReDoS
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
Upgrade to 0.1.12.
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.
