Bug 1882329 (CVE-2020-15168) - CVE-2020-15168 node-fetch: size of data after fetch() JS thread leads to DoS
Summary: CVE-2020-15168 node-fetch: size of data after fetch() JS thread leads to DoS
Keywords:
Status: NEW
Alias: CVE-2020-15168
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1883144 1883146 1883143 1883145 1883147 1883384
Blocks: 1882331
TreeView+ depends on / blocked
 
Reported: 2020-09-24 10:40 UTC by Dhananjay Arunesh
Modified: 2020-09-29 01:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2020-09-24 10:40:20 UTC
A vulnerability was found in 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.

References:
https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
https://www.npmjs.com/package/node-fetch


Note You need to log in before you can comment on or make changes to this bug.