Auth bypass in Auth0 Jsonwebtoken
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.4 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L.
EPSS exploit prediction
EPSS 0.006, 47.8th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Auth0 Jsonwebtoken
- Auth0 Node-Jsonwebtoken — versions <= 8.5.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
Also mentioned in 7 other repositories (ARPSyndicate/cvemon, k0mi-tg/CVE-POC, manas3c/CVE-POC, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
This CVE has public exploit evidence. See the latest CVEs with public exploits.