CVE-2022-23540

Medium

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.

SeverityMedium
CVSS6.4
Exploit probability—
ProductAuth0 Jsonwebtoken
PublishedDec 22, 2022
First seenDec 22, 2022

How to fix

Update
  • jsonwebtoken9.0.0 or later

Affected products

ProductAffected versionsFixed in
auth0 jsonwebtokenv ≤ 8.5.1—
jsonwebtokennpmv < 9.0.09.0.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.