CVE-2020-15168

low-risk
Published 2020-09-10

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.

Do I need to act?

-
0.11% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
2
CVSS 2.6/10 Low
NETWORK / HIGH complexity

Affected Products (6)

Node-Fetch
Node-Fetch
Node-Fetch
Node-Fetch
Node-Fetch
Node-Fetch

Affected Vendors

Node-Fetch Project

References (4)

Third Party Advisory https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
Product https://www.npmjs.com/package/node-fetch
Third Party Advisory https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
Product https://www.npmjs.com/package/node-fetch
23
/ 100
low-risk
Severity 10/34 · Low
Exploitability 0/34 · Minimal
Exposure 13/34 · Low