CVE-2020-15168
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.
How to fix
- node-fetch_project node-fetch2.6.1 or later
- node-fetch2.6.1, 3.0.0-beta.9 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| node-fetch_project node-fetch | v < 2.6.1, 3.0.0 | 2.6.1 |
| node-fetchnpm | 2.0.0 ≤ v < 2.6.1, 3.0.0-beta.1 ≤ v < 3.0.0-beta.9 | 2.6.1, 3.0.0-beta.9 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.