Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(package): Update dependency node-fetch to v2.6.7 [SECURITY] #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 29, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.3.0 -> 2.6.7 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.

CVE-2022-0235

node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor


Release Notes

node-fetch/node-fetch

v2.6.7

Compare Source

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

Compare Source

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.5

Compare Source

v2.6.4

Compare Source

v2.6.3

Compare Source

v2.6.2

Compare Source

fixed main path in package.json

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


  • 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 renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 83c6f0d to 4c01fbc Compare February 11, 2021 10:11
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 4c01fbc to 12a43f1 Compare February 22, 2021 12:18
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to v2.6.1 [SECURITY] chore(package): Update dependency node-fetch to ^2.6.1 [SECURITY] Feb 22, 2021
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 12a43f1 to 91fb29c Compare February 25, 2021 12:45
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to ^2.6.1 [SECURITY] chore(package): Update dependency node-fetch to v2.6.1 [SECURITY] Feb 25, 2021
@renovate
Copy link
Contributor Author

renovate bot commented Mar 2, 2021

⚠️ 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 check 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: package-lock.json

@renovate renovate bot changed the title chore(package): Update dependency node-fetch to v2.6.1 [SECURITY] chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] Mar 4, 2021
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] - autoclosed Jun 10, 2021
@renovate renovate bot closed this Jun 10, 2021
@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch June 10, 2021 02:44
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] - autoclosed chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] Jun 10, 2021
@renovate renovate bot reopened this Jun 10, 2021
@renovate renovate bot restored the renovate/npm-node-fetch-vulnerability branch June 10, 2021 03:52
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 91fb29c to f25eab7 Compare June 10, 2021 04:03
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to 2.6.1 [SECURITY] chore(package): Update dependency node-fetch to 2.6.7 [SECURITY] Sep 25, 2022
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from f25eab7 to 3b88563 Compare September 25, 2022 16:53
@renovate renovate bot changed the title chore(package): Update dependency node-fetch to 2.6.7 [SECURITY] chore(package): Update dependency node-fetch to v2.6.7 [SECURITY] Mar 24, 2023
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.

0 participants