Quick answers
- Is CVE-2020-28495 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-28495 being exploited in the wild.
- How severe is CVE-2020-28495?
- Low severity, with a CVSS score of 3.1, published 5 February 2021.
- Which products and versions are affected?
- total.js (npm) SEMVER:introduced=0,fixed=3.4.7.
- Is there a fix for CVE-2020-28495?
- Yes. total.js (npm): upgrade to 3.4.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-28495 attacked?
- It is attacked over the network.
- Am I affected by CVE-2020-28495?
- Check whether you run total.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
- total.js (npm): upgrade to 3.4.7 or later
npm install total.js@3.4.7
Technical details
The vulnerability is a prototype pollution flaw (CWE-1321) in the total.js set() utility function that fails to properly sanitize path keys when setting values into objects. An attacker can craft a malicious path string containing prototype pollution sequences (such as "__proto__" or "constructor.prototype") to pollute the Object prototype. The attack requires network access and no authentication, but impact depends on the application's usage patterns. Versions before 3.4.7 are affected; the fix adds validation to reject paths that target prototype properties.
Affected products
- total.js total.js before 3.4.7
Identifiers
- CVE-2020-28495
- GHSA-6cf8-qhqj-vjqm
Timeline
- 2021-02-05: disclosed
- 2021-02-03: patched: Fixed in version 3.4.7