CVE-2020-15168
Summary
| CVE | CVE-2020-15168 |
|---|
| State | PUBLIC |
|---|
| Assigner | [email protected] |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2020-09-10 19:15:00 UTC |
|---|
| Updated | 2020-09-17 20:21:00 UTC |
|---|
| 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. |
|---|
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| node-fetch |
MISC |
www.npmjs.com |
Product, Third Party Advisory |
| The `size` option isn't honored after following a redirect · Advisory · node-fetch/node-fetch · GitHub |
CONFIRM |
github.com |
Third Party Advisory |
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 983209 Nodejs (npm) Security Update for node-fetch (GHSA-w7rc-rwvf-8q5r)
