| Name | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 970173 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| node-fetch (PTS) | bullseye | 2.6.1-5+deb11u1 | fixed |
| bookworm | 3.3.0+~cs11.4.11-2 | fixed | |
| sid, trixie | 3.3.2+~cs11.4.11-3 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| node-fetch | source | experimental | 2.6.1-1 | |||
| node-fetch | source | (unstable) | 2.6.1-2 | 970173 |
[buster] - node-fetch <ignored> (Minor issue; Intrusive to backport)
https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r