CVEvulnerability

CVE-2020-15168

5.3 MEDIUM Published 2020-09-10 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2020-09-10
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
2.6 LOW — CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
CVSS 3.1 ([email protected])
5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS 2.0 ([email protected])
5.0 MEDIUM — AV:N/AC:L/Au:N/C:N/I:N/A:P
Weaknesses
CWE-20, CWE-770

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.

Affected configurations

• node-fetch project node-fetch (< 2.6.1) • node-fetch project node-fetch 3.0.0

Related

Weakness · CWE (2)

  • CWE-20 Improper Input Validation weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

References