Advisory

GHSA-w7rc-rwvf-8q5r

Also known as: CVE-2020-15168

Summary

The size option isn't honored after following a redirect in node-fetch

Details

Impact
Node Fetch 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.

Patches
We released patched versions for both stable and beta channels:

  • For v2: 2.6.1
  • For v3: 3.0.0-beta.9

Workarounds
None, it is strongly recommended to update as soon as possible.

For more information
If you have any questions or comments about this advisory:

  • Open an issue in node-fetch
  • Contact one of the core maintainers.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2020-09-10 17:46 UTC
Modified
2026-07-08 06:00 UTC

Affected packages and fixes

node-fetch

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.6.1 (semver)

Fixed versions

2.6.1

Fix

node-fetch

npm · All systems

Affected

  • introduced 3.0.0-beta.1, fixed 3.0.0-beta.9 (semver)

Fixed versions

3.0.0-beta.9

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences