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.
References
Link | Resource |
---|---|
https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3 | Patch Third Party Advisory |
https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-8cf7-32gw-wr33 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20240621-0007/ |
Configurations
History
21 Jun 2024, 19:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
07 Nov 2023, 03:44
Type | Values Removed | Values Added |
---|---|---|
Summary | 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. |
Information
Published : 2022-12-23 00:15
Updated : 2024-06-21 19:15
NVD link : CVE-2022-23539
Mitre link : CVE-2022-23539
CVE.ORG link : CVE-2022-23539
JSON object : View
Products Affected
auth0
- jsonwebtoken
CWE
CWE-327
Use of a Broken or Risky Cryptographic Algorithm