Security readout for executives and security teams
Plain-English summary
CVE-2021-4229 concerns malicious ua-parser-js releases that introduced a crypto-mining backdoor. Organizations exposed through affected dependency versions should treat this as a supply-chain compromise, not a routine bug. The source bundle names fixed versions, so remediation is direct: identify use, upgrade, and verify deployed artifacts no longer contain the affected releases.
Executive priority
Treat this as high priority where the dependency is present. Even with a medium CVSS score, a confirmed malicious dependency release can affect build integrity, operational trust, and incident response scope.
Technical view
Affected ua-parser-js versions 0.7.29, 0.8.0, and 1.0.0 include a crypto-mining backdoor component, classified as CWE-912. The CVSS v3.1 score provided is 5.0, but the issue has critical operational significance because dependency installation or deployment can introduce malicious code. Fixed versions are 0.7.30, 0.8.1, and 1.0.1.
Likely exposure
Exposure is likely for applications, build systems, or deployed artifacts that used ua-parser-js 0.7.29, 0.8.0, or 1.0.0. Transitive dependency use should be checked through lockfiles, SBOMs, and dependency scanners.
Exploitation context
The sources describe malicious affected releases containing a crypto-mining backdoor. The bundle does not show CISA KEV listing or cited evidence of ongoing active exploitation, so current exploitation should not be asserted from this evidence alone.
Researcher notes
Evidence is strongest for version identification and fixed releases. The source bundle does not include detailed indicators, exploit telemetry, or cleanup specifics beyond upgrading. Validation should focus on dependency provenance, transitive inclusion, deployed artifact contents, and whether affected versions ever entered build or runtime environments.
Mitigation direction
- Upgrade ua-parser-js to 0.7.30, 0.8.1, 1.0.1, or later.
- Remove affected versions from manifests, lockfiles, caches, and build artifacts.
- Rebuild and redeploy from clean dependency resolution after upgrading.
- Check vendor advisories for any additional cleanup guidance.
- Prioritize systems that installed dependencies during the affected release window.
Validation and detection
- Search SBOMs and lockfiles for ua-parser-js 0.7.29, 0.8.0, or 1.0.0.
- Confirm production artifacts resolve to fixed ua-parser-js versions.
- Review dependency scanner output for GHSA-pjwm-rvh2-c87w or CVE-2021-4229.
- Check build and deployment inventories for systems that consumed affected releases.
- Document any exposed environments and remediation evidence.
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-912: 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-2021-4229 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
- Medium
- CVSS
- 5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
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.
CVSS vector scores
1 official scoreWe 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:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L1.63.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/advisories/GHSA-pjwm-rvh2-c87wCVE reference · x_refsource_MISC
- https://github.com/faisalman/ua-parser-js/issues/536CVE reference · x_refsource_MISC
- https://vuldb.com/?id.185453CVE reference · x_refsource_MISC
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.
Hidden Functionality
Hidden Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.