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

2020-09-1018:25:13

CWE-20

CWE-770

GitHub_M

www.cve.org

2.6 Low

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

LOW

User Interaction

REQUIRED

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

LOW

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

6.2 Medium

AI Score

Confidence

High

0.001 Low

EPSS

Percentile

42.5%

JSON

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.

CNA Affected

[
  {
    "product": "node-fetch",
    "vendor": "node-fetch",
    "versions": [
      {
        "status": "affected",
        "version": "<2.6.1"
      },
      {
        "status": "affected",
        "version": ">3.0.0-beta.1, <3.0.0-beta.9"
      }
    ]
  }
]