CVE Vulnerability

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.

9.8 /10

CVSS v3.0 : CRITICAL

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6 Third Party Advisory
https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3 Patch Third Party Advisory
Configurations

Configuration 1

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

Published : 2022-12-22 07:15

Updated : 2022-12-29 08:07

NVD link : CVE-2022-23540

Mitre link : CVE-2022-23540

Products Affected
No products.
CWE
CWE-327