CVE-2022-23539 jsonwebtoken unrestricted key type could lead to legacy keys usage

2022-12-2223:20:47

CWE-327

GitHub_M

www.cve.org

jsonwebtoken

vulnerability

legacy keys

security advisory

update

5.9 Medium

CVSS3

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

LOW

Integrity Impact

HIGH

Availability Impact

NONE

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

0.001 Low

EPSS

Percentile

41.1%

JSON

Versions <=8.5.1 of jsonwebtoken library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key type other than a combination listed in the GitHub Security Advisory as unaffected. This issue has been fixed, please update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, if you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the allowInvalidAsymmetricKeyTypes option to true in the sign() and/or verify() functions.

CNA Affected

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