node-fetch up to 2.6.0/3.0.0-beta.8 Size allocation of resources

Summaryinfo

A vulnerability classified as problematic was found in node-fetch up to 2.6.0/3.0.0-beta.8. This vulnerability affects the function fetch of the component Size Handler. Executing a manipulation can lead to allocation of resources. This vulnerability appears as CVE-2020-15168. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in node-fetch up to 2.6.0/3.0.0-beta.8. It has been declared as problematic. This vulnerability affects the function fetch of the component Size Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes:

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.

The weakness was presented 09/10/2020 (GitHub Repository). The advisory is available at github.com. This vulnerability was named CVE-2020-15168 since 06/25/2020. The exploitation appears to be difficult. The attack can be initiated remotely. The successful exploitation requires a single authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 2.6.1 or 3.0.0.beta.9 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• node-fetch

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6.0
• 3.0.0-beta.0
• 3.0.0-beta.1
• 3.0.0-beta.2
• 3.0.0-beta.3
• 3.0.0-beta.4
• 3.0.0-beta.5
• 3.0.0-beta.6
• 3.0.0-beta.7
• 3.0.0-beta.8

Website

• Product: https://github.com/node-fetch/node-fetch/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion