CVE-2022-23540
MEDIUMAuth0 Jsonwebtoken < 8.5.1 - Authentication Bypass
Title source: ruleDescription
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 (3)
Core 3
Core References
Third Party Advisory x_refsource_confirm
https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6
Patch x_refsource_misc
https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3
Vendor Advisory
https://security.netapp.com/advisory/ntap-20240621-0007/
Scores
CVSS v3
6.4
EPSS
0.0002
EPSS Percentile
5.7%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
CISA SSVC
Vulnrichment
Exploitation
none
Automatable
no
Technical Impact
partial
Details
CWE
CWE-287
CWE-347
Status
published
Products (2)
auth0/jsonwebtoken
< 8.5.1
npm/jsonwebtoken
0 - 9.0.0npm
Published
Dec 22, 2022
Tracked Since
Feb 18, 2026