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:
bitinn/node-fetch
### [`v2.6.1`](https://togithub.com/bitinn/node-fetch/releases/v2.6.1)
[Compare Source](https://togithub.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1)
**This is an important security release. It is strongly recommended to update as soon as possible.**
See [CHANGELOG](https://togithub.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261) for details.
Renovate configuration
:date: Schedule: "" (UTC).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
2.6.0
->2.6.1
GitHub Vulnerability Alerts
CVE-2020-15168
Impact
Node Fetch did not honor the
size
option after following a redirect, which means that when a content size was over the limit, aFetchError
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:
v2
: 2.6.1v3
: 3.0.0-beta.9Workarounds
None, it is strongly recommended to update as soon as possible.
For more information
If you have any questions or comments about this advisory:
Release Notes
bitinn/node-fetch
### [`v2.6.1`](https://togithub.com/bitinn/node-fetch/releases/v2.6.1) [Compare Source](https://togithub.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1) **This is an important security release. It is strongly recommended to update as soon as possible.** See [CHANGELOG](https://togithub.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261) for details.Renovate configuration
:date: Schedule: "" (UTC).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.