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

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2022-12-22T23:20:47.855Z

Updated: 2024-08-03T03:43:46.551Z

Reserved: 2022-01-19T21:23:53.795Z

Link: CVE-2022-23539

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2022-12-23T00:15:12.347

Modified: 2024-11-21T06:48:46.303

Link: CVE-2022-23539

cve-icon Redhat

Severity : Moderate

Publid Date: 2022-12-23T00:00:00Z

Links: CVE-2022-23539 - Bugzilla