Quick answers
- Is CVE-2021-4229 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-4229 being exploited in the wild.
- How severe is CVE-2021-4229?
- High severity, with a CVSS score of 8.8, published 22 October 2021.
- Which products and versions are affected?
- ua-parser-js (npm) SEMVER:introduced=0.7.29,fixed=0.7.30.
- Is there a fix for CVE-2021-4229?
- Yes. ua-parser-js (npm): upgrade to 0.7.30 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2021-4229 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2021-4229?
- Check whether you run ua-parser-js (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ua-parser-js (npm): upgrade to 0.7.30 or later
npm install ua-parser-js@0.7.30
Technical details
The npm package 'ua-parser-js' suffered a supply chain attack where versions 0.7.29, 0.8.0, and 1.0.0 were published containing malicious code (CWE-506). The malware is designed to execute upon installation or runtime, potentially granting attackers full control over the host environment. This allows for the exfiltration of environment variables, secrets, and authentication keys. The vulnerability is triggered via a network-based delivery of the malicious package, though it requires the user to perform an installation or update (User Interaction). Patched versions 0.7.30, 0.8.1, and 1.0.1 have been released to remediate the issue.
Affected products
- faisalman ua-parser-js 0.7.29, 0.8.0, 1.0.0
Identifiers
- CVE-2021-4229
- GHSA-pjwm-rvh2-c87w
Timeline
- 2021-10-22: disclosed
- 2021-10-22: advisory
- 2021-10-22: patched