Skip to content

Update dependency node-fetch to v2.6.1 [SECURITY] - abandoned#6

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-node-fetch-vulnerability
Open

Update dependency node-fetch to v2.6.1 [SECURITY] - abandoned#6
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-node-fetch-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Jan 23, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.3.0 -> 2.6.1 age adoption passing confidence

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, 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.

Release Notes

node-fetch/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.


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate-approve[bot]
renovate-approve bot previously approved these changes Jan 23, 2021
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 8d6412e to 51102be Compare March 7, 2022 14:10
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 7, 2022
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 51102be to ab34e06 Compare April 24, 2022 19:09
renovate-approve[bot]
renovate-approve bot previously approved these changes Apr 24, 2022
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from ab34e06 to 31ecc00 Compare May 16, 2022 00:01
@renovate
Copy link
Copy Markdown
Author

renovate bot commented May 16, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
This script must be run as root

@renovate
Copy link
Copy Markdown
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot changed the title Update dependency node-fetch to v2.6.1 [SECURITY] Update dependency node-fetch to v2.6.1 [SECURITY] - abandoned May 29, 2023
@renovate
Copy link
Copy Markdown
Author

renovate bot commented May 29, 2023

Autoclosing Skipped

This 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants