Update dependency node-fetch to v2.6.1 [SECURITY] #183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
b75fa62
to
168e703
Compare
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
168e703
to
afbe552
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
afbe552
to
efe7d54
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
efe7d54
to
d3d7982
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
2.6.0->2.6.1GitHub Vulnerability Alerts
CVE-2020-15168
Impact
Node Fetch did not honor the
sizeoption after following a redirect, which means that when a content size was over the limit, aFetchErrorwould 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
node-fetch/node-fetch
v2.6.1Compare Source
This is an important security release. It is strongly recommended to update as soon as possible.
See CHANGELOG for details.
Configuration
📅 Schedule: "" (UTC).
🚦 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.