minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern
isaacs minimatch
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| minimatch npm |
|
isaacs minimatch
| Product | Affected | Fixed in |
|---|---|---|
| minimatch npm |
|
10.2.19.0.68.0.57.4.76.2.15.1.74.2.43.1.3minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions 10.2.0 and below are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS. This issue has been fixed in version 10.2.1.
From the CVE record · GitHub_M
Affected minimatch versions can spend excessive time matching a glob pattern with many consecutive * wildcards followed by a literal character absent from the test string. An attacker who can supply the pattern argument to an application's minimatch() call can cause a denial of service; the input does not specify whether authentication or other user interaction is required.
Check applications using npm minimatch versions >=10.0.0 <10.2.1, >=9.0.0 <9.0.6, >=8.0.0 <8.0.5, >=7.0.0 <7.4.7, >=6.0.0 <6.2.1, >=5.0.0 <5.1.7, >=4.0.0 <4.2.4, or <3.1.3.