CVE-2022-23540

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

State
Published
Severity
6.4 Medium
Published
Dec 22, 2022
Updated
Feb 13, 2025
Reserved
Jan 19, 2022

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.16.4 MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LGitHub_M

Weaknesses

Affected Products

ProductVersions
node-jsonwebtokenauth0
  • <= 8.5.1Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.