fix: security vulnerability in JWT for Node.JS (CVE-2022-23529) #69
Conversation
This file contains 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.
name: "Hotfix Report"
about: "Report on a hotfix for a security flaw in Node.JS"
title: "Hotfix Report: Security flaw in Node.JS JWT"
labels: "security, hotfix, Node.JS"
Hotfix Report
Current behavior
A serious security flaw in the JWT used in Node.JS (CVE-2022-23529) [https://nvd.nist.gov/vuln/detail/CVE-2022-23529] was recently discovered. This flaw allows invaders to access the recovery key parameter of the jwt.verify function, which can compromise the server where the resource is hosted.
To protect your widely used project as a standard among developers, we recommend that you update the dependency or find a way to bypass this issue.
Possible Solution
Upgrade to jsonwebtoken@9.0.0