Vulnerabilities · 2022 · Auth0
CVE-2022-23539
Auth0 Jsonwebtoken vulnerability
Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key type other than a combination listed in the GitHub Security Advisory as unaffected. This issue has been fixed, please update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, if you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the `allowInvalidAsymmetricKeyTypes` option to `true` in the `sign()` and/or `verify()` functions.
Affected products
Jsonwebtoken. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Auth0 Jsonwebtoken runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3 · Patch
- github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-8cf7-32gw-wr33 · Third Party Advisory
- security.netapp.com/advisory/ntap-20240621-0007/
- nvd.nist.gov/vuln/detail/CVE-2022-23539
- security.netapp.com/advisory/ntap-20240621-0007
- github.com/advisories/GHSA-8cf7-32gw-wr33
- nvd.nist.gov/vuln/detail/CVE-2022-23539
- cve.org/CVERecord?id=CVE-2022-23539
More vulnerabilities in Auth0 products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.