Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/peer_dependency_mismatch_no_lockfile/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
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.
Vulnerable Library - fetch-factory-0.0.1.tgz
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/peer_dependency_mismatch_no_lockfile/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2022-0235
### Vulnerable Library - node-fetch-1.6.3.tgzA light-weight module that brings window.fetch to node.js and io.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
Dependency Hierarchy: - fetch-factory-0.0.1.tgz (Root Library) - isomorphic-fetch-2.2.1.tgz - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
Found in base branch: main
### 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,3.1.1
CVE-2020-15168
### Vulnerable Library - node-fetch-1.6.3.tgzA light-weight module that brings window.fetch to node.js and io.js
Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.6.3.tgz
Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/package.json
Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/yanked_version/node_modules/node-fetch,/npm_and_yarn/spec/fixtures/projects/yarn/optional_dependencies/node_modules/node-fetch
Dependency Hierarchy: - fetch-factory-0.0.1.tgz (Root Library) - isomorphic-fetch-2.2.1.tgz - :x: **node-fetch-1.6.3.tgz** (Vulnerable Library)
Found in base branch: main
### 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 (2.6)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: Required - 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: 2.6.1,3.0.0-beta.9