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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2022-12-22T18:02:24.770Z

Updated: 2024-08-03T03:43:46.466Z

Reserved: 2022-01-19T21:23:53.795Z

Link: CVE-2022-23540

cve-icon Vulnrichment

Updated: 2024-08-03T03:43:46.466Z

cve-icon NVD

Status : Modified

Published: 2022-12-22T19:15:08.967

Modified: 2024-11-21T06:48:46.437

Link: CVE-2022-23540

cve-icon Redhat

Severity : Moderate

Publid Date: 2022-12-22T00:00:00Z

Links: CVE-2022-23540 - Bugzilla