In codecov (npm package) before version 3.7.1 the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was issued but the fix was incomplete. It only blocked &, and command injection is still possible using backticks instead to bypass the sanitizer. The attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-0235
### Vulnerable Library - node-fetch-2.6.0.tgz
A light-weight module that brings window.fetch to node.js
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2020-15168
### Vulnerable Library - node-fetch-2.6.0.tgz
A light-weight module that brings window.fetch to node.js
node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Uploading report to Codecov: https://codecov.io
Library home page: https://registry.npmjs.org/codecov/-/codecov-3.7.0.tgz
Path to dependency file: /tmp/ws-scm/racing-bars-history/package.json
Path to vulnerable library: /racing-bars-history/node_modules/codecov/package.json
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2020-15123
### Vulnerable Library - codecov-3.7.0.tgzUploading report to Codecov: https://codecov.io
Library home page: https://registry.npmjs.org/codecov/-/codecov-3.7.0.tgz
Path to dependency file: /tmp/ws-scm/racing-bars-history/package.json
Path to vulnerable library: /racing-bars-history/node_modules/codecov/package.json
Dependency Hierarchy: - :x: **codecov-3.7.0.tgz** (Vulnerable Library)
Found in base branch: develop
### Vulnerability DetailsIn codecov (npm package) before version 3.7.1 the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was issued but the fix was incomplete. It only blocked &, and command injection is still possible using backticks instead to bypass the sanitizer. The attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.
Publish Date: 2020-07-20
URL: CVE-2020-15123
### CVSS 3 Score Details (9.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/codecov/codecov-node/security/advisories/GHSA-xp63-6vf5-xf3v
Release Date: 2020-07-27
Fix Resolution: 3.7.1
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-0235
### Vulnerable Library - node-fetch-2.6.0.tgzA light-weight module that brings window.fetch to node.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.0.tgz
Path to dependency file: /tmp/ws-scm/racing-bars-history/package.json
Path to vulnerable library: /tmp/ws-scm/racing-bars-history/node_modules/node-fetch/package.json
Dependency Hierarchy: - codecov-3.7.0.tgz (Root Library) - teeny-request-6.0.1.tgz - :x: **node-fetch-2.6.0.tgz** (Vulnerable Library)
Found in base branch: develop
### Vulnerability Detailsnode-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Publish Date: 2022-01-16
URL: CVE-2022-0235
### CVSS 3 Score Details (6.1)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-r683-j2x4-v87g
Release Date: 2022-01-16
Fix Resolution (node-fetch): 2.6.7
Direct dependency fix Resolution (codecov): 3.7.1
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2020-15168
### Vulnerable Library - node-fetch-2.6.0.tgzA light-weight module that brings window.fetch to node.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.0.tgz
Path to dependency file: /tmp/ws-scm/racing-bars-history/package.json
Path to vulnerable library: /tmp/ws-scm/racing-bars-history/node_modules/node-fetch/package.json
Dependency Hierarchy: - codecov-3.7.0.tgz (Root Library) - teeny-request-6.0.1.tgz - :x: **node-fetch-2.6.0.tgz** (Vulnerable Library)
Found in base branch: develop
### Vulnerability Detailsnode-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Publish Date: 2020-09-10
URL: CVE-2020-15168
### CVSS 3 Score Details (5.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
Release Date: 2020-09-17
Fix Resolution (node-fetch): 2.6.1
Direct dependency fix Resolution (codecov): 3.7.1
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)