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)
Published · last modified .
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.
EPSS exploit prediction
EPSS 0.017, 77.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Node-Fetch — versions <2.6.1, >3.0.0-beta.1, <3.0.0-beta.9
- Node-Fetch Project — versions 3.0.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 3 other repositories (404notf0und/CVE-Flow, k1LoW/oshka, therickybobbeh/dep-scanner). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r (Third Party Advisory)
- www.npmjs.com/package/node-fetch (Product, Third Party Advisory)