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 (76.2th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 76th percentile — 76.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-15168: held from 0.017 to 0.017.

EPSS over last 30 days · oldest: 0.017 · newest: 0.017 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

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.