Skip to content

Update dependency path-to-regexp to v6.3.0 [SECURITY]#222

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-path-to-regexp-vulnerability
Open

Update dependency path-to-regexp to v6.3.0 [SECURITY]#222
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-path-to-regexp-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 10, 2024

This PR contains the following updates:

Package Change Age Confidence
path-to-regexp 6.2.26.3.0 age confidence

path-to-regexp outputs backtracking regular expressions

CVE-2024-45296 / GHSA-9wv6-86v2-598j

More information

Details

Impact

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.

Patches

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.

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 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.

Details

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.

References

Severity

  • CVSS Score: 7.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

pillarjs/path-to-regexp (path-to-regexp)

v6.3.0: Fix backtracking in 6.x

Compare Source

Fixed


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from nzws as a code owner September 10, 2024 17:41
@vercel
Copy link
Copy Markdown

vercel Bot commented Sep 10, 2024

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
knzklive2-web Ready Ready Preview, Comment Apr 27, 2026 10:10pm

@renovate renovate Bot changed the title Update dependency path-to-regexp to v8 [SECURITY] Update dependency path-to-regexp to v8 [SECURITY] - autoclosed Sep 12, 2024
@renovate renovate Bot closed this Sep 12, 2024
@renovate renovate Bot deleted the renovate/npm-path-to-regexp-vulnerability branch September 12, 2024 18:46
@renovate renovate Bot changed the title Update dependency path-to-regexp to v8 [SECURITY] - autoclosed Update dependency path-to-regexp to v8 [SECURITY] Sep 12, 2024
@renovate renovate Bot reopened this Sep 12, 2024
@renovate renovate Bot restored the renovate/npm-path-to-regexp-vulnerability branch September 12, 2024 21:29
@renovate renovate Bot changed the title Update dependency path-to-regexp to v8 [SECURITY] Update dependency path-to-regexp to v6.3.0 [SECURITY] Sep 12, 2024
@renovate renovate Bot force-pushed the renovate/npm-path-to-regexp-vulnerability branch from 4e0e7c7 to 5a8f094 Compare September 12, 2024 21:29
@renovate renovate Bot changed the title Update dependency path-to-regexp to v6.3.0 [SECURITY] Update dependency path-to-regexp to v6.3.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/npm-path-to-regexp-vulnerability branch March 27, 2026 01:08
@renovate renovate Bot changed the title Update dependency path-to-regexp to v6.3.0 [SECURITY] - autoclosed Update dependency path-to-regexp to v6.3.0 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-path-to-regexp-vulnerability branch 2 times, most recently from 5a8f094 to e5bca17 Compare March 30, 2026 22:05
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Mar 30, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedpath-to-regexp@​6.3.010010010094100

View full report

@renovate renovate Bot changed the title Update dependency path-to-regexp to v6.3.0 [SECURITY] Update dependency path-to-regexp to v6.3.0 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency path-to-regexp to v6.3.0 [SECURITY] - autoclosed Update dependency path-to-regexp to v6.3.0 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-path-to-regexp-vulnerability branch 2 times, most recently from e5bca17 to 2040563 Compare April 27, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants