Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Auth0 | Jsonwebtoken | <= 8.5.1 |
Related Weaknesses (CWE)
References
- https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1bPatch
- https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xThird Party Advisory
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1bPatch
- https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xThird Party Advisory
- https://security.netapp.com/advisory/ntap-20240621-0007/
FAQ
What is CVE-2022-23540?
CVE-2022-23540 is a vulnerability with a CVSS score of 6.4 (MEDIUM). 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 signa...
How severe is CVE-2022-23540?
CVE-2022-23540 has been rated MEDIUM with a CVSS base score of 6.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-23540?
Check the references section above for vendor advisories and patch information. Affected products include: Auth0 Jsonwebtoken.