You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NPM package micromatch is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
dlabrecq
changed the title
Bug - eslint-plugin-patternfly-react - vulnerability
Bug - eslint-plugin-patternfly-react - vulnerability 1 of 2
May 29, 2024
dlabrecq
changed the title
Bug - eslint-plugin-patternfly-react - vulnerability 1 of 2
Bug - eslint-plugin-patternfly-react - micromatch vulnerability
May 29, 2024
Cost Management inherits
micromatch
fromeslint-plugin-patternfly-react
, which has the vulnerability described below.Red Hat requires a by 12-Aug-2024
See https://issues.redhat.com/browse/COST-5041
Flaw:
CVE-2024-4067 micromatch: vulnerable to Regular Expression Denial of Service
https://bugzilla.redhat.com/show_bug.cgi?id=2280601
The NPM package
micromatch
is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs inmicromatch.braces()
inindex.js
because the pattern.*
will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.https://devhub.checkmarx.com/cve-details/CVE-2024-4067/
https://github.com/micromatch/micromatch/blob/2c56a8604b68c1099e7bc0f807ce0865a339747a/index.js#L448
micromatch/micromatch#243
micromatch/micromatch#247
Output from
npm why micromatch
The text was updated successfully, but these errors were encountered: