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

Sun, 08 Sep 2024 18:15:00 +0000

Type Values Removed Values Added
First Time appeared Redhat
Redhat acm
CPEs cpe:/a:redhat:acm:2.2::el7
Vendors & Products Redhat
Redhat acm

Mon, 19 Aug 2024 22:00:00 +0000

Type Values Removed Values Added
CPEs cpe:/a:redhat:acm:2.2::el7
cpe:/a:redhat:acm:2.2::el8
Vendors & Products Redhat
Redhat acm

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2020-09-10T18:25:13

Updated: 2024-08-04T13:08:22.463Z

Reserved: 2020-06-25T00:00:00

Link: CVE-2020-15168

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2020-09-10T19:15:13.490

Modified: 2020-09-17T20:21:19.147

Link: CVE-2020-15168

cve-icon Redhat

Severity : Low

Publid Date: 2020-09-10T00:00:00Z

Links: CVE-2020-15168 - Bugzilla