CVE-2022-23540 — Improper Authentication

Vendor	Product	Version range	Fixed in
auth0	jsonwebtoken	<= 8.5.1	—
auth0	jsonwebtoken	>= 0 < 9.0.0	9.0.0
auth0	node-jsonwebtoken	<= 8.5.1	—

Red Hat

jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass

vendor_redhat·2022-12-22·CVSS 6.4

CVE-2022-23540 [MEDIUM] CWE-327 jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass 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. A flaw was found in the jsonwebtoken library. In

GHSA

jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

ghsa·2022-12-22

CVE-2022-23540 [MEDIUM] CWE-287 jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify() jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify() # Overview In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition and a falsy secret or key in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. # Am I affected? You will be affected if all the following are true in the `jwt.verify()` function: - a token with no signature is received - no algorithms are specified - a falsy (e.g. null, false, undefined) secret or key is passed # How do I fix it? Update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. # Will the fix impact my users? There will be no impact, if you update t

OSV

jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

osv·2022-12-22

CVE-2022-23540 [MEDIUM] jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify() jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify() # Overview In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition and a falsy secret or key in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. # Am I affected? You will be affected if all the following are true in the `jwt.verify()` function: - a token with no signature is received - no algorithms are specified - a falsy (e.g. null, false, undefined) secret or key is passed # How do I fix it? Update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. # Will the fix impact my users? There will be no impact, if you update t

CVE-2022-23540: 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…

Affected

CVSS provenance