Quick answers
- Is CVE-2020-7596 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-7596 being exploited in the wild.
- How severe is CVE-2020-7596?
- Low severity, with a CVSS score of 3.1, published 24 May 2022.
- Which products and versions are affected?
- codecov (npm) SEMVER:introduced=0,fixed=3.6.2.
- Is there a fix for CVE-2020-7596?
- Yes. codecov (npm): upgrade to 3.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-7596 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-7596?
- Check whether you run codecov (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
- codecov (npm): upgrade to 3.6.2 or later
npm install codecov@3.6.2
Technical details
The Codecov npm module before version 3.6.2 fails to properly neutralize special elements in the "gcov-args" input parameter, allowing command injection via improper output handling in a downstream component (CWE-74). An authenticated attacker or malicious build configuration can inject shell metacharacters into the gcov-args argument, which are then executed by the system shell during code coverage processing. This requires either network access to a system running Codecov or control over build configuration/environment. An attacker can achieve arbitrary command execution in the context of the user running Codecov, potentially exfiltrating credentials or compromising the build pipeline. The vulnerability was fixed in version 3.6.2.
Affected products
- Codecov codecov < 3.6.2
Identifiers
- CVE-2020-7596
- GHSA-mh2h-6j8q-x246
Timeline
- 2020-01-25: disclosed: NVD published date
- 3.6.2: patched: Fix version released