Bug 1224367

Summary: VUL-0: CVE-2024-4067: velociraptor: the npm package `micromatch` is vulnerable to Regular Expression Denial of Service (ReDoS)
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Antonio Teixeira <antonio.teixeira>
Status: NEW --- QA Contact: Security Team bot <security-team>
Severity: Major    
Priority: P3 - Medium CC: gabriele.sonnu
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/405384/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-4067:7.5:(AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 1224255    

Description SMASH SMASH 2024-05-16 12:47:19 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-4067
https://www.cve.org/CVERecord?id=CVE-2024-4067
https://devhub.checkmarx.com/cve-details/CVE-2024-4067/
https://github.com/micromatch/micromatch/blob/2c56a8604b68c1099e7bc0f807ce0865a339747a/index.js#L448
https://github.com/micromatch/micromatch/issues/243
https://github.com/micromatch/micromatch/pull/247
Comment 1 Gabriele Sonnu 2024-05-16 12:47:37 UTC
Vulnerable versions of the micromatch package are embedded in:

- SUSE:ALP:Source:Standard:1.0/velociraptor  micromatch (4.0.2, 4.0.4)

Upstream issue:

https://github.com/micromatch/micromatch/issues/243