Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2021

This PR contains the following updates:

Package Change Age Confidence
node-fetch 2.3.0 -> 2.6.7 age confidence

GitHub Vulnerability Alerts

CVE-2022-0235

node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.

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


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

This PR was generated by Mend Renovate. View the repository job log.

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

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 c21759d to db7647f Compare March 7, 2022 12:17
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from db7647f to 519e393 Compare April 24, 2022 21:18
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 519e393 to 55de484 Compare June 18, 2022 23:20
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.1 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Sep 25, 2022
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 55de484 to c1bc76e Compare January 23, 2025 21:25
@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from c1bc76e to 123e4f3 Compare January 30, 2025 19:33
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