Security readout for executives and security teams
Plain-English summary
A flaw in @eslint/plugin-kit versions before 0.2.3 can let maliciously crafted input consume excessive CPU and crash the affected process. The primary business risk is service or tooling disruption, not disclosed data theft or modification.
Executive priority
Prioritize remediation for internet-facing or shared services where untrusted input reaches this package. Upgrade promptly during the next expedited maintenance window; isolated developer tooling is lower urgency but should still be updated.
Technical view
Improper input sanitization permits regular-expression denial of service in @eslint/plugin-kit before 0.2.3. Processing malicious input can cause excessive CPU consumption and process failure. The record maps this to CWE-1333 and CWE-770 and assigns CVSS 4.0 score 8.7, driven by high availability impact.
Likely exposure
Exposure exists where version 0.2.2 or earlier is installed directly or transitively and attacker-controlled input can reach the vulnerable processing path. The bundle does not identify specific applications, deployment patterns, or whether typical ESLint usage is remotely reachable.
Exploitation context
The supplied record is not in CISA KEV. Its CVSS vector reports network reachability, low complexity, no privileges, no user interaction, and proof-of-concept maturity. This supports credible denial-of-service risk but does not establish active exploitation.
Researcher notes
The sources identify a ReDoS condition and a fixing commit, but the supplied bundle does not describe the precise input grammar, vulnerable call path, affected downstream products, or observed attacks. Validate reachability through dependency and data-flow analysis without stress-testing production systems.
Mitigation direction
- Upgrade @eslint/plugin-kit to version 0.2.3 or later.
- Update dependency lockfiles so vulnerable transitive versions are no longer resolved.
- Restrict untrusted input from reaching affected processing until upgrades are complete.
- Check upstream ESLint guidance before applying additional mitigations.
Validation and detection
- Inventory direct and transitive installations of @eslint/plugin-kit.
- Confirm production and build environments resolve version 0.2.3 or later.
- Review input paths to determine whether untrusted data reaches the package.
- Monitor affected processes for unusual CPU spikes, hangs, or crashes.
- Verify dependency scans no longer report CVE-2024-21539.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-770: 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.
Open ATT&CK lookupCVE-2024-21539 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P——snykCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P3.93.6snykVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://security.snyk.io/vuln/SNYK-JS-ESLINTPLUGINKIT-8340627CVE reference, snyk
- https://github.com/eslint/rewrite/commit/071be842f0bd58de4863cdf2ab86d60f49912abfCVE reference, snyk
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.