minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressions
isaacs minimatch
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| minimatch npm |
|
isaacs minimatch
| Product | Affected | Fixed in |
|---|---|---|
| minimatch npm |
|
10.2.39.0.78.0.67.4.86.2.25.1.84.2.53.1.4minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested `*()` extglobs produce regexps with nested unbounded quantifiers (e.g. `(?:(?:a|b)*)*`), which exhibit catastrophic backtracking in V8. With a 12-byte pattern `*(*(*(a|b)))` and an 18-byte non-matching input, `minimatch()` stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default `minimatch()` API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects `+()` extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue.
From the CVE record · GitHub_M
Nested `*()` and `+()` extglobs in affected minimatch versions can cause catastrophic regex backtracking through the default `minimatch()` API. An attacker who can supply a glob pattern and non-matching input to an application using minimatch could stall processing; the input does not specify whether that access is network-based or requires authentication or user interaction.
Engineers running npm minimatch should check versions below 3.1.4 and versions 4.0.0–4.2.4, 5.0.0–5.1.7, 6.0.0–6.2.1, 7.0.0–7.4.7, 8.0.0–8.0.5, 9.0.0–9.0.6, or 10.0.0–10.2.2.