Update dependency node-fetch to v2 [SECURITY] #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.3.0
->^2.0.0
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
Compare Source
This is an important security release. It is strongly recommended to update as soon as possible.
See CHANGELOG for details.
v2.6.0
Compare Source
See CHANGELOG.
v2.5.0
Compare Source
See CHANGELOG.
v2.4.1
Compare Source
See CHANGELOG.
v2.4.0
Compare Source
See CHANGELOG.
v2.3.0
Compare Source
See CHANGELOG.
v2.2.1
Compare Source
See CHANGELOG.
v2.2.0
Compare Source
v2.1.2
Compare Source
Body
methods to work on ArrayBuffer-backed
Body` objectsBody
methods when the accumulatedBuffer
exceeds the maximum sizeHost
headers with any casingfetch()
from TypeScript inbrowser.js
See CHANGELOG.
v2.1.1
Compare Source
See CHANGELOG.
Fix packaging errors in version 2.1.0.
v2.1.0
Compare Source
See CHANGELOG:
body
of afetch()
orRequest
Headers
object internally with the given case, for compatibility with older servers that incorrectly treated header names in a case-sensitive mannerLocation
header just like non-redirect responsesv2.0.0
Compare Source
This is a major release. See upgrade guide on how to upgrade from v1.x, and the changelog for all changes.
Renovate configuration
馃搮 Schedule: "" in timezone Europe/Stockholm.
馃殾 Automerge: Disabled by config. Please merge this manually once you are satisfied.
鈾伙笍 Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
馃敃 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.