jsonwebtoken unrestricted key type could lead to legacy keys usage
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| auth0 | node-jsonwebtoken | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| RHODF-4.12-RHEL-8 | |||
| odf4/mcg-core-rhel8:v4.12.3-4 | cpe:/a:redhat:openshift_data_foundation:4.12::el8 | RHSA-2023:3265 | 2023-05-23T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-7563 | 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. |
Github GHSA |
GHSA-8cf7-32gw-wr33 | jsonwebtoken unrestricted key type could lead to legacy keys usage |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.524% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | jsonwebtoken unrestricted key type could lead to legacy keys usage | jsonwebtoken unrestricted key type could lead to legacy keys usage |