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 CVE-2020-15168

To remediate CVE-2020-15168, upgrade the affected package to a fixed version below.

• —upgrade to 2.6.1-2 or later
• —upgrade to 2.6.1 or later

Is CVE-2020-15168 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 2.6.1-2
• >= 2.0.0, < 2.6.1

CVSS scores

References (6)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2020-15168
• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2020-15168
• PATCHgithub.com/node-fetch/node-fetch
• WEBgithub.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334