CVE-2020-15168
File size limit bypass in node-fetch
- State
- Published
- Severity
- 2.6 Low
- Published
- Sep 10, 2020
- Updated
- Aug 4, 2024
- Reserved
- Jun 25, 2020
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 2.6 Low | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L | GitHub_M |
Weaknesses
Affected Products
| Product | Versions |
|---|---|
node-fetchnode-fetch |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.