CVE-2024-21538: Versions of the package cross-spawn before 6.0.6, from 7.0.0 and before 7.0.5 are vulnerable to Regular Exp...
Versions of the package cross-spawn before 6.0.6, from 7.0.0 and before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.
Security readout for executives and security teams
Plain-English summary
A flaw in affected cross-spawn versions can let an attacker consume excessive CPU and crash an application by supplying an unusually large, specially crafted string. The primary business risk is service disruption, not data theft or modification.
Executive priority
Prioritize remediation for internet-facing or multi-tenant services where untrusted input reaches cross-spawn. Other deployments should follow routine high-severity dependency remediation after confirming reachability. Escalate if service crashes or unexplained CPU spikes are observed.
Technical view
CVE-2024-21538 is a CWE-1333 regular-expression denial-of-service vulnerability caused by improper input sanitization. A crafted string can trigger excessive regex processing, raising CPU usage and potentially terminating the process. The supplied CVSS 4.0 score is 8.7, with high availability impact.
Likely exposure
Exposure is most significant where vulnerable cross-spawn versions are directly or transitively installed and attacker-controlled strings can reach the affected processing path. Package presence alone does not prove remote exploitability; application data flow and reachability must be assessed.
Exploitation context
The supplied record is not listed in KEV and provides no evidence of active exploitation. Its CVSS vector reports proof-of-concept maturity. Public code changes are available, but they do not establish widespread or in-the-wild attacks.
Researcher notes
The source bundle identifies affected ranges as versions before 6.0.6 and 7.0.0 through 7.0.4. Its separate affected-product summaries are less precise, especially for the WebJar artifact. Validate package coordinates, resolved versions, and actual input flow before declaring exposure.
Mitigation direction
Upgrade pre-6.0.6 installations to 6.0.6 or a later supported release.
Upgrade 7.0.0 through 7.0.4 installations to 7.0.5 or later.
Update lockfiles and rebuild deployed artifacts to remove vulnerable transitive copies.
For the WebJar package, confirm the corrected release using its vendor guidance.
Restrict untrusted input from affected processing paths until upgrades are deployed.
Validation and detection
Inventory direct and transitive cross-spawn versions in lockfiles, SBOMs, and deployed artifacts.
Confirm no versions below 6.0.6 or from 7.0.0 through 7.0.4 remain.
Trace whether externally controlled strings can reach code using the affected dependency.
Verify rebuilt production artifacts contain the intended corrected dependency version.
Run controlled availability and regression tests without using production systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1333: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1333 · source CWE mapping
Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.