CVE-2024-4067

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.

CVSS v3 5.3 MEDIUM

5.3^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 3.9 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact LOW

Scope UNCHANGED

References

Link	Resource
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

Configurations

No configuration.

History

No history.

Information

Published : 2024-05-14 15:42

Updated : 2024-05-22 12:15

NVD link : CVE-2024-4067

Mitre link : CVE-2024-4067

CVE.ORG link : CVE-2024-4067

JSON object : View

Products Affected

No product.

CWE

CWE-1333

Inefficient Regular Expression Complexity

{"id": "CVE-2024-4067", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2024-05-14T15:42:47.947", "references": [{"url": "https://devhub.checkmarx.com/cve-details/CVE-2024-4067/", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"}, {"url": "https://github.com/micromatch/micromatch/blob/2c56a8604b68c1099e7bc0f807ce0865a339747a/index.js#L448", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"}, {"url": "https://github.com/micromatch/micromatch/issues/243", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"}, {"url": "https://github.com/micromatch/micromatch/pull/247", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647", "description": [{"lang": "en", "value": "CWE-1333"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "El paquete NPM `micromatch` es vulnerable a la denegaci\u00f3n de servicio de expresi\u00f3n regular (ReDoS). La vulnerabilidad ocurre en `micromatch.braces()` en `index.js` porque el patr\u00f3n `.*` coincidir\u00e1 con avidez con cualquier cosa. Al pasar un payload malicioso, la coincidencia de patrones seguir\u00e1 retrocediendo hasta la entrada hasta que no encuentre el corchete de cierre. A medida que aumenta el tama\u00f1o de la entrada, el tiempo de consumo tambi\u00e9n aumentar\u00e1 hasta provocar que la aplicaci\u00f3n se cuelgue o se ralentice. Hubo una soluci\u00f3n combinada, pero pruebas adicionales muestran que el problema persiste. Este problema se debe mitigar mediante el uso de un patr\u00f3n seguro que no comience a retroceder la expresi\u00f3n regular debido a coincidencias codiciosas."}], "lastModified": "2024-05-22T12:15:10.767", "sourceIdentifier": "596c5446-0ce5-4ba2-aa66-48b3b757a647"}