Update dependency jsonwebtoken to v9 [SECURITY]#67
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-jsonwebtoken-vulnerability
branch
2 times, most recently
from
1720a4f to
38a32c6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^8.0.0→^9.0.0jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()
CVE-2022-23540 / GHSA-qwph-4952-7xr6
More information
Details
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 thenonealgorithm for signature verification.Am I affected?
You will be affected if all the following are true in the
jwt.verify()function: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
nonealgorithm. If you need 'none' algorithm, you have to explicitly specify that injwt.verify()options.Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
auth0/node-jsonwebtoken (jsonwebtoken)
v9.0.0Compare Source
Breaking changes: See Migration from v8 to v9
Breaking changes
8345030]8345030)ecdf6cc]ecdf6cc)Security fixes
Arbitrary File Write via verify function- CVE-2022-23529Insecure default algorithm in jwt.verify() could lead to signature validation bypass- CVE-2022-23540Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC- CVE-2022-23541Unrestricted key type could lead to legacy keys usage- CVE-2022-23539v8.5.1Compare Source
Bug fix
Docs
v8.5.0Compare Source
New Functionality
Test Improvements
Docs
v8.4.0Compare Source
New Functionality
Bug Fixes
Docs
Test Improvements
CI
v8.3.0Compare Source
v8.2.2Compare Source
v8.2.1Compare Source
v8.2.0Compare Source
v8.1.1Compare Source
v8.1.0Compare Source
v8.0.1Compare Source
lodash.isarraydependency (#394) (7508e8957cb1c778f72fa9a363a7b135b3c9c36d)Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.