CVE-2020-15168
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| node-fetch | node-fetch | <2.6.1 | affected |
| node-fetch | node-fetch | >3.0.0-beta.1, <3.0.0-beta.9 | affected |
Weaknesses
- CWE-20: CWE-20: Improper Input Validation
- CWE-770: CWE-770 Allocation of Resources Without Limits or Throttling
ADP Enrichment
CVE Program Container
Additional References
- https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
- https://www.npmjs.com/package/node-fetch
References
- https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
- https://www.npmjs.com/package/node-fetch
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.