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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 22, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-fetch 2.6.2 -> 2.6.7 age adoption passing 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.


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


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 changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 23, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 24, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 24, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 24, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 24, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 24, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 25, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 25, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 25, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] Mar 25, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] Mar 27, 2023
@renovate renovate bot changed the title Update dependency node-fetch to v2.6.7 [SECURITY] Update dependency node-fetch to 2.6.7 [SECURITY] May 17, 2023
@renovate renovate bot changed the title Update dependency node-fetch to 2.6.7 [SECURITY] Update dependency node-fetch to v2.6.7 [SECURITY] May 28, 2023
@erwinmombay
Copy link
Member

@Vue-Pu heya. we appreciate any contribution but just a warning to stop approving Pull Requests that you are not associated with or working on please, as it is not very helpful or constructive

@renovate renovate bot force-pushed the renovate/npm-node-fetch-vulnerability branch from 0803fcd to b7bc04d Compare December 1, 2023 04:27
Copy link
Contributor Author

renovate bot commented Dec 1, 2023

⚠ 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: package-lock.json
ERROR: npm v10.2.4 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.2.4/node_modules/npm/node_modules/@npmcli/agent/lib/agents.js:105
    options.lookup ??= this.#options.lookup
                   ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.2.4/node_modules/npm/node_modules/@npmcli/agent/lib/index.js:7:15)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
ERROR: npm v10.2.4 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.2.4/node_modules/npm/node_modules/@npmcli/agent/lib/agents.js:105
    options.lookup ??= this.#options.lookup
                   ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.2.4/node_modules/npm/node_modules/@npmcli/agent/lib/index.js:7:15)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)

@renovate renovate bot changed the base branch from future to static-production-amp-dev December 1, 2023 04:27
@powerivq powerivq closed this Jan 3, 2024
Copy link
Contributor Author

renovate bot commented Jan 3, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (2.6.7). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/npm-node-fetch-vulnerability branch January 3, 2024 23:44
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.

3 participants