CVE-2022-23540

high

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.

References

https://security.netapp.com/advisory/ntap-20240621-0007/

https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6

https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3

Details

Source: Mitre, NVD

Published: 2022-12-22

Updated: 2026-06-17

Risk Information

CVSS v2

Base Score: 8

Vector: CVSS2#AV:N/AC:L/Au:S/C:P/I:C/A:P

Severity: High

CVSS v3

Base Score: 7.6

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

Severity: High

EPSS

EPSS: 0.00021