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

fix(deps): update dependency jsonwebtoken to v9 [security] #39

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jsonwebtoken ^8.5.1 -> ^9.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-23540

Overview

In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition and a falsy secret or key in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification.

Am I affected?

You will be affected if all the following are true in the jwt.verify() function:

  • a token with no signature is received
  • no algorithms are specified
  • a falsy (e.g. null, false, undefined) secret or key is passed

How do I fix it?

Update to version 9.0.0 which removes the default support for the none algorithm in the jwt.verify() method.

Will the fix impact my users?

There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the none algorithm. If you need 'none' algorithm, you have to explicitly specify that in jwt.verify() options.


Release Notes

auth0/node-jsonwebtoken (jsonwebtoken)

v9.0.0

Compare Source

Breaking changes: See Migration from v8 to v9

Breaking changes
Security fixes
  • security: fixes Arbitrary File Write via verify function - CVE-2022-23529
  • security: fixes Insecure default algorithm in jwt.verify() could lead to signature validation bypass - CVE-2022-23540
  • security: fixes Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC - CVE-2022-23541
  • security: fixes Unrestricted key type could lead to legacy keys usage - CVE-2022-23539

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title fix(deps): update dependency jsonwebtoken to v9 [security] fix(deps): update dependency jsonwebtoken to v9 [security] - autoclosed Feb 24, 2024
@renovate renovate bot closed this Feb 24, 2024
@renovate renovate bot deleted the renovate/npm-jsonwebtoken-vulnerability branch February 24, 2024 07:59
@renovate renovate bot changed the title fix(deps): update dependency jsonwebtoken to v9 [security] - autoclosed fix(deps): update dependency jsonwebtoken to v9 [security] Feb 24, 2024
@renovate renovate bot reopened this Feb 24, 2024
@renovate renovate bot restored the renovate/npm-jsonwebtoken-vulnerability branch February 24, 2024 09:05
@renovate renovate bot force-pushed the renovate/npm-jsonwebtoken-vulnerability branch from 139690e to b2e97fc Compare February 24, 2024 09:05
@renovate renovate bot changed the title fix(deps): update dependency jsonwebtoken to v9 [security] fix(deps): update dependency jsonwebtoken to v9 [security] - autoclosed Jul 18, 2024
@renovate renovate bot closed this Jul 18, 2024
@renovate renovate bot deleted the renovate/npm-jsonwebtoken-vulnerability branch July 18, 2024 21:26
@renovate renovate bot restored the renovate/npm-jsonwebtoken-vulnerability branch July 19, 2024 01:41
@renovate renovate bot changed the title fix(deps): update dependency jsonwebtoken to v9 [security] - autoclosed fix(deps): update dependency jsonwebtoken to v9 [security] Jul 19, 2024
@renovate renovate bot reopened this Jul 19, 2024
@renovate renovate bot force-pushed the renovate/npm-jsonwebtoken-vulnerability branch from b2e97fc to ba0f270 Compare July 19, 2024 01:41
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