Skip to content
Fencer Vulns
low 2.6

CVE-2020-15168 json

File size limit bypass in node-fetch

published 2020-09-10 6 y ago modified 2026-07-08 4 mo ago also GHSA-w7rc-rwvf-8q5r , EUVD-2020-1335

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

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.

Patch / fix

  • npm node-fetch 2.6.1, 3.0.0-beta.9
  • node-fetch_project node-fetch 2.6.1
  • node-fetch Debian 14, Debian 13, Debian 12 2.6.1-2

debian advisories DEBIAN-CVE-2020-15168

  • spacecmd Manager Server Module 4.1, Manager Proxy Module 4.1 4.1.8-4.9.2
  • mgr-daemon Manager Proxy Module 4.1 4.1.3-2.6.3
  • pxe-formula Manager Server Module 4.1 0.1.1602490840.4f32148-3.3.2
  • susemanager Manager Server Module 4.1 4.1.21-3.11.6
  • bind-formula Manager Server Module 4.1 0.1.1603299886.60e4bcf-3.3.2
  • spacewalk-web Manager Server Module 4.1, Manager Proxy Module 4.1 4.1.19-3.9.5
  • spacewalk-java Manager Server Module 4.1 4.1.22-3.16.4
  • grafana-formula Manager Server Module 4.1 0.3.0-3.3.2

suse advisories SUSE-SU-2020:3235-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-15168 updated cvss 5.3

node-fetch: size of data after fetch() JS thread leads to DoS

  • Red Hat Advanced Cluster Management for Kubernetes 2 node-fetch
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm node-fetch
>=2.0.0, <2.6.1
>=3.0.0-beta.1, <3.0.0-beta.9
2.6.1
3.0.0-beta.9

Affected products

  • node-fetch node-fetch

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.