-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz #120
Labels
security vulnerability
Security vulnerability detected by WhiteSource
Comments
mend-bolt-for-github
bot
added
the
security vulnerability
Security vulnerability detected by WhiteSource
label
Oct 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Oct 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz
Oct 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Nov 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz
Nov 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Nov 28, 2020
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Jan 23, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Jan 23, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Jan 23, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Feb 1, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Feb 1, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Feb 9, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
May 9, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
May 9, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Jun 6, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Jun 6, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
Jun 6, 2021
mend-bolt-for-github
bot
changed the title
CVE-2020-15168 (Medium) detected in node-fetch-2.6.0.tgz, node-fetch-1.7.3.tgz
CVE-2020-15168 (Medium) detected in node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
Jun 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CVE-2020-15168 - Medium Severity Vulnerability
Vulnerable Libraries - node-fetch-1.7.3.tgz, node-fetch-2.6.0.tgz
node-fetch-1.7.3.tgz
A 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.7.3.tgz
Path to dependency file: sync-stripe-to-moltin/package.json
Path to vulnerable library: sync-stripe-to-moltin/node_modules/node-fetch/package.json
Dependency Hierarchy:
node-fetch-2.6.0.tgz
A 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: sync-stripe-to-moltin/package.json
Path to vulnerable library: sync-stripe-to-moltin/node_modules/@octokit/request/node_modules/node-fetch/package.json
Dependency Hierarchy:
Found in HEAD commit: e9650d462a45749f4043665c4c77fe1c04cbd5ba
Vulnerability Details
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.
Publish Date: 2020-09-10
URL: CVE-2020-15168
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-w7rc-rwvf-8q5r
Release Date: 2020-07-21
Fix Resolution: 2.6.1,3.0.0-beta.9
Step up your Open Source Security Game with WhiteSource here
The text was updated successfully, but these errors were encountered: