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

2022-12-2218:02:24

CWE-287

GitHub_M

www.cve.org

jsonwebtokens

signature bypass

version 8.5.1

algorithm definition

update to 9.0.0

6.4 Medium

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

LOW

Integrity Impact

HIGH

Availability Impact

LOW

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L

7.7 High

AI Score

Confidence

High

0.001 Low

EPSS

Percentile

34.5%

JSON

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.

CNA Affected

[
  {
    "vendor": "auth0",
    "product": "node-jsonwebtoken",
    "versions": [
      {
        "version": "<= 8.5.1",
        "status": "affected"
      }
    ]
  }
]