Resource exhaustion in Node-Fetch
CVE-2020-15168
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.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
EPSS: 0.017 (74.7th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 2.6 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L.
Affected products
- Node-fetch — versions <2.6.1, >3.0.0-beta.1, <3.0.0-beta.9
- Node-fetch_project Node-fetch — versions 3.0.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security-advisories@github.com (x_refsource_CONFIRM, Third Party Advisory)
- security-advisories@github.com (Product, Third Party Advisory, x_refsource_MISC)
Frequently asked questions
- What is CVE-2020-15168?
- CVE-2020-15168 is a low-severity vulnerability in Node-Fetch, classified under Improper Input Validation. CVSS score: 2.6/10. Published 2020-09-10.
- How severe is CVE-2020-15168?
- Low severity. CVSS v3 base score is 2.6 out of 10.
- Is CVE-2020-15168 known to be exploited?
- 3 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.