Vulnerability · Published Sep 10, 2020 · Assigned by GitHub_M

CVE-2020-15168File size limit bypass in node-fetch

Low 2.6

In plain English

A low-severity improper input validation in node-fetch from node-fetch. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.7% (higher than 77% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)2.6Low
Exploit odds (30 days)1.7%top 22.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12node-fetch2.6.1-2DEBIAN-CVE-2020-15168
Debian:13node-fetch2.6.1-2DEBIAN-CVE-2020-15168
Debian:14node-fetch2.6.1-2DEBIAN-CVE-2020-15168
npmnode-fetch2.6.1GHSA-w7rc-rwvf-8q5r
npmnode-fetch3.0.0-beta.9GHSA-w7rc-rwvf-8q5r

Affected products (as reported)

VendorProductVersions
node-fetch node-fetch <2.6.1>3.0.0-beta.1, <3.0.0-beta.9

Weakness: CWE-20, CWE-770 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

References