CVE-2022-23540

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.

Weakness classification

• security-advisories@github.com: CWE-287
• nvd@nist.gov: CWE-347

Primary references

• security-advisories@github.com — Patch
• security-advisories@github.com — Third Party Advisory
• security-advisories@github.com
• af854a3a-2127-422b-91ae-364da2661108 — Patch
• af854a3a-2127-422b-91ae-364da2661108 — Third Party Advisory
• af854a3a-2127-422b-91ae-364da2661108