Vulnerability Database
289,697
Total vulnerabilities in the database
CVE-2020-15168
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.
| Software | From | Fixed in |
|---|---|---|
| node-fetch_project / node-fetch | - | 2.6.1 |
| node-fetch_project / node-fetch | 3.0.0-beta1 | 3.0.0-beta1.x |
| node-fetch_project / node-fetch | 3.0.0-beta5 | 3.0.0-beta5.x |
| node-fetch_project / node-fetch | 3.0.0-beta6 | 3.0.0-beta6.x |
| node-fetch_project / node-fetch | 3.0.0-beta7 | 3.0.0-beta7.x |
| node-fetch_project / node-fetch | 3.0.0-beta8 | 3.0.0-beta8.x |
node-fetch
|
- | 2.6.1 |
|
node-fetch
|
3.0.0-beta.1 | 3.0.0-beta.9 |