Skip to content

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

low severity Published Sep 10, 2020 in node-fetch/node-fetch • Updated Jan 7, 2021
We are still processing this advisory. You may have affected repositories that are not yet on this list. Check back soon for more.

Package

npm node-fetch (npm)

Affected versions

< 2.6.1
>= 3.0.0-beta.1, <= 3.0.0-beta.8

Patched versions

2.6.1
3.0.0-beta.9

Description

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.

References

@xxczaki xxczaki published the maintainer security advisory Sep 9, 2020

CVE ID

CVE-2020-15168

CVSS Score

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

Credits