Skip to content

CVE-2022-23540 jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

HighCVSS 7.6 EPSS 0.57%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification. Users are affected if you do not specify algorithms in the jwt.verify() function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the jwt.verify() method. 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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
auth0 jsonwebtoken <= 8.5.1 after 8.5.1 Fixed
npm jsonwebtoken(npm) < 9.0.0 9.0.0 Fixed
auth0 node-jsonwebtoken = <= 8.5.1 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
npm jsonwebtoken(npm) < 9.0.0 9.0.0
auth0 node-jsonwebtoken = <= 8.5.1 No fix listed
auth0 jsonwebtoken <= 8.5.1 No fix listed

References