Vulnerability Description
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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Node-Fetch Project | Node-Fetch | < 2.6.1 |
Related Weaknesses (CWE)
References
- https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5rThird Party Advisory
- https://www.npmjs.com/package/node-fetchProductThird Party Advisory
- https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5rThird Party Advisory
- https://www.npmjs.com/package/node-fetchProductThird Party Advisory
FAQ
What is CVE-2020-15168?
CVE-2020-15168 is a vulnerability with a CVSS score of 2.6 (LOW). 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...
How severe is CVE-2020-15168?
CVE-2020-15168 has been rated LOW with a CVSS base score of 2.6/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-15168?
Check the references section above for vendor advisories and patch information. Affected products include: Node-Fetch Project Node-Fetch.