CVE-2022-23540

2022-12-2219:15:08

CWE-347

CWE-287

[email protected]

web.nvd.nist.gov

130

cve-2022-23540

jsonwebtoken

signature validation

bypass

algorithm

jwt.verify

security

update

7.6 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

LOW

Integrity Impact

HIGH

Availability Impact

LOW

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

7.3 High

AI Score

Confidence

High

0.001 Low

EPSS

Percentile

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

Affected configurations

Vulners

NVD

Node

auth0jsonwebtokenRange≤8.5.1

VendorProductVersionCPE
auth0jsonwebtoken*cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:*:*:*

Vendor	Product	Version	CPE
auth0	jsonwebtoken	*	cpe:2.3:a:auth0:jsonwebtoken::::::::

CNA Affected

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