Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. node-fetch
  4. ›
  5. CVE-2020-15168

CVE-2020-15168: Allocation of Resources Without Limits or Throttling

September 10, 2020 (updated September 17, 2020)

node-fetch 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.

References

  • nvd.nist.gov/vuln/detail/CVE-2020-15168

Code Behaviors & Features

Detect and mitigate CVE-2020-15168 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 2.6.1, version 3.0.0

Fixed versions

  • 2.6.1

Solution

Upgrade to version 2.6.1 or above.

Impact 5.3 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Learn more about CVSS

Weakness

  • CWE-770: Allocation of Resources Without Limits or Throttling

Source file

npm/node-fetch/CVE-2020-15168.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:26 +0000.