Update dependency node-fetch to 2.6.7 [SECURITY] - abandoned#296
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Update dependency node-fetch to 2.6.7 [SECURITY] - abandoned#296renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
6368a02 to
5f3c78a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
2 times, most recently
from
6ff6add to
b0ef927
Compare
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
3 times, most recently
from
222f173 to
d32f5f2
Compare
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
7 times, most recently
from
96da2d0 to
c9cc40d
Compare
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
6 times, most recently
from
7ba9de7 to
2bb9660
Compare
renovate
bot
force-pushed
the
renovate/npm-node-fetch-vulnerability
branch
from
2bb9660 to
242acf6
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.7GitHub Vulnerability Alerts
CVE-2022-0235
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
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:
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 Mend Renovate. View repository job log here.