CVE-2020-15168GHSA-W7RC-RWVF-8Q5R
File size limit bypass in node-fetch
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.6.1, 3.0.0-beta.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- node-fetch node-fetch
fixed in 2.6.1; From 3.0.0-beta.1 · fixed in 3.0.0-beta.9
- node-fetchnpm
From 2.0.0 · fixed in 2.6.1
- node-fetchnpm
From 3.0.0-beta.1 · fixed in 3.0.0-beta.9