CVE-2020-15168
Node-fetch Project Node-fetch vulnerability
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.
Affected products
Node-fetch. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Node-fetch Project Node-fetch runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r · Third Party Advisory
- www.npmjs.com/package/node-fetch · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-15168
- github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334
- github.com/node-fetch/node-fetch/commit/eaff0094c4dfdd5b78711a8c4f1b61e33d282072
- github.com/advisories/GHSA-w7rc-rwvf-8q5r
- nvd.nist.gov/vuln/detail/CVE-2020-15168
- cve.org/CVERecord?id=CVE-2020-15168
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.