fkie_cve-2024-4068
Vulnerability from fkie_nvd
Published
2024-05-14 15:42
Modified
2024-11-21 09:42
Severity ?
Summary
The NPM package `braces`, versions prior to 3.0.3, fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In `lib/parse.js,` if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
References
Impacted products
Vendor | Product | Version |
---|
{ cveTags: [], descriptions: [ { lang: "en", value: "The NPM package `braces`, versions prior to 3.0.3, fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In `lib/parse.js,` if a malicious user sends \"imbalanced braces\" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.", }, { lang: "es", value: "El paquete NPM \"braces\" no limita la cantidad de caracteres que puede manejar, lo que podría provocar agotamiento de la memoria. En `lib/parse.js`, si un usuario malintencionado envía \"imbalanced braces\" como entrada, el análisis entrará en un bucle, lo que hará que el programa comience a asignar memoria de montón sin liberarla en ningún momento del bucle. Finalmente, se alcanza el límite del montón de JavaScript y el programa fallará.", }, ], id: "CVE-2024-4068", lastModified: "2024-11-21T09:42:07.710", metrics: { cvssMetricV31: [ { cvssData: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "HIGH", baseScore: 7.5, baseSeverity: "HIGH", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.1", }, exploitabilityScore: 3.9, impactScore: 3.6, source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", type: "Secondary", }, ], }, published: "2024-05-14T15:42:48.660", references: [ { source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", url: "https://devhub.checkmarx.com/cve-details/CVE-2024-4068/", }, { source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", url: "https://github.com/micromatch/braces/commit/415d660c3002d1ab7e63dbf490c9851da80596ff", }, { source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", url: "https://github.com/micromatch/braces/issues/35", }, { source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", url: "https://github.com/micromatch/braces/pull/37", }, { source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", url: "https://github.com/micromatch/braces/pull/40", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "https://devhub.checkmarx.com/cve-details/CVE-2024-4068/", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "https://github.com/micromatch/braces/commit/415d660c3002d1ab7e63dbf490c9851da80596ff", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "https://github.com/micromatch/braces/issues/35", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "https://github.com/micromatch/braces/pull/37", }, { source: "af854a3a-2127-422b-91ae-364da2661108", url: "https://github.com/micromatch/braces/pull/40", }, ], sourceIdentifier: "596c5446-0ce5-4ba2-aa66-48b3b757a647", vulnStatus: "Awaiting Analysis", weaknesses: [ { description: [ { lang: "en", value: "CWE-1050", }, ], source: "596c5446-0ce5-4ba2-aa66-48b3b757a647", type: "Secondary", }, { description: [ { lang: "en", value: "CWE-400", }, ], source: "134c704f-9b21-4f2e-91b3-4a467353bcc0", type: "Secondary", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.