Quick answers
- Is CVE-2020-7719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-7719 being exploited in the wild.
- How severe is CVE-2020-7719?
- Low severity, with a CVSS score of 3.1, published 6 May 2021.
- Which products and versions are affected?
- locutus (npm) SEMVER:introduced=0,fixed=2.0.12.
- Is there a fix for CVE-2020-7719?
- Yes. locutus (npm): upgrade to 2.0.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-7719 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-7719?
- Check whether you run locutus (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
- locutus (npm): upgrade to 2.0.12 or later
npm install locutus@2.0.12
Technical details
Locutus versions prior to 2.0.12 are vulnerable to prototype pollution via the php.strings.parse_str function. The vulnerability occurs when processing untrusted input that is parsed as URL-encoded query strings, allowing an attacker to inject malicious property names (e.g., __proto__, constructor) that modify the Object prototype. This is a CWE-1321 / CWE-915 vulnerability requiring only network access and no authentication. An attacker can poison the prototype chain to affect all objects in the application's runtime, potentially leading to privilege escalation, code execution, or denial of service. The vulnerability was patched in version 2.0.12, available via pull request #418.
Affected products
- locutus locutus all versions prior to 2.0.12
Identifiers
- CVE-2020-7719
- GHSA-f98m-q3hr-p5wq
Timeline
- 2020-09-01: disclosed
- 2020-09-03: patched: Security fix merged in PR #418
- 2021-05-06: advisory: GHSA advisory published