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.

Sign up for GitHub

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

Jump to bottom

Update dependency node-fetch to v2.6.7 [SECURITY] #26

Open

renovate wants to merge 1 commit into master from renovate/npm-node-fetch-vulnerability

renovate bot commented Oct 26, 2020 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
node-fetch	`2.3.0` -> `2.6.7`

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`

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

fix: don't forward secure headers to 3th party by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/1453

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

`v2.6.6`

What's Changed

fix(URL): prefer built in URL version when available and fallback to whatwg by @jimmywarting in https://github.com/node-fetch/node-fetch/pull/1352

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

`v2.6.5`

`v2.6.4`

`v2.6.3`

`v2.6.2`

fixed main path in package.json

`v2.6.1`

This is an important security release. It is strongly recommended to update as soon as possible.

See CHANGELOG for details.

`v2.6.0`

`v2.5.0`

`v2.4.1`

`v2.4.0`

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 bot changed the title ~~Update dependency node-fetch to v2.6.1 [SECURITY]~~ Update dependency node-fetch to 2.6.1 [SECURITY]


          Update dependency node-fetch to 2.6.7 [SECURITY]

637b5b3

renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 48c82f5 to 637b5b3 Compare

September 25, 2022 15:03

renovate bot changed the title ~~Update dependency node-fetch to 2.6.1 [SECURITY]~~ Update dependency node-fetch to 2.6.7 [SECURITY]

renovate bot changed the title ~~Update dependency node-fetch to 2.6.7 [SECURITY]~~ Update dependency node-fetch to v2.6.7 [SECURITY]

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

Labels

None yet