CVE-2022-23540

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:node.js:*:*

History

21 Nov 2024, 06:48

Type Values Removed Values Added
References () https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3 - Patch () https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3 - Patch
References () https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6 - Third Party Advisory () https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6 - Third Party Advisory
References () https://security.netapp.com/advisory/ntap-20240621-0007/ - () https://security.netapp.com/advisory/ntap-20240621-0007/ -
CVSS v2 : unknown
v3 : 7.6
v2 : unknown
v3 : 6.4

21 Jun 2024, 19:15

Type Values Removed Values Added
References
  • () https://security.netapp.com/advisory/ntap-20240621-0007/ -

07 Nov 2023, 03:44

Type Values Removed Values Added
Summary 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. 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.

14 Jul 2023, 19:22

Type Values Removed Values Added
CWE CWE-327 CWE-347

Information

Published : 2022-12-22 19:15

Updated : 2024-11-21 06:48


NVD link : CVE-2022-23540

Mitre link : CVE-2022-23540

CVE.ORG link : CVE-2022-23540


JSON object : View

Products Affected

auth0

  • jsonwebtoken
CWE
CWE-287

Improper Authentication

CWE-347

Improper Verification of Cryptographic Signature