CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2022 · Auth0

CVE-2022-23540
Auth0 Jsonwebtoken vulnerability

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.

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

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.