CVE-2020-15168

unknown
Published 2020-09-10 ยท Modified 2026-03-13
CVSS v3
โ€”
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
โ€”

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.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OSVersionStatusFixed in
debian debianbookwormfixed2.6.1-2
debian debianbullseyefixed2.6.1-2
debian debianforkyfixed2.6.1-2
debian debiansidfixed2.6.1-2
debian debiantrixiefixed2.6.1-2

Package impact

EcosystemPackageVulnerableFixed
npm npmnode-fetch>=2.0.0,<2.6.12.6.1
npm npmnode-fetch>=3.0.0-beta.1,<3.0.0-beta.93.0.0-beta.9

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.