CVE-2022-23541 jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC

2022-12-2217:52:22

CWE-1259

CWE-287

GitHub_M

github.com

json web tokens

insecure implementation

key retrieval

rsa

hmac

misconfigured library

incorrect verification

asymmetric key

symmetric key

key retrieval function

patched version

5 Medium

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

LOW

Integrity Impact

LOW

Availability Impact

LOW

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

6.6 Medium

AI Score

Confidence

Low

JSON

jsonwebtoken is an implementation of JSON Web Tokens. Versions <= 8.5.1 of jsonwebtoken library can be misconfigured so that passing a poorly implemented key retrieval function referring to the secretOrPublicKey argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.

CNA Affected

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