Skip to content
Fencer Intel
medium 5.9

CVE-2022-23539 json

jsonwebtoken unrestricted key type could lead to legacy keys usage

published 3y ago modified 4mo ago also GHSA-8cf7-32gw-wr33 , EUVD-2022-7563

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

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.

Patch / fix

  • npm jsonwebtoken 9.0.0

Is CVE-2022-23539 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-23539 updated cvss 8.1

jsonwebtoken: Unrestricted key type could lead to legacy keys usagen

  • Red Hat OpenShift Container Platform 4 openshift4/ose-console
    affected: no fix planned “Will not fix”
  • Red Hat Openshift Container Storage 4 ocs4/mcg-core-rhel8
    affected: no fix planned “Out of support scope”
  • Red Hat Openshift Data Foundation 4 noobaa-core-container
    affected: no fix available
  • Red Hat RHODF 4.12 for RHEL 8 odf4/mcg-core-rhel8 v4.12.3-4
    fixed: vendor fix RHSA-2023:3265
  • Red Hat RHODF 4.12 for RHEL 8 odf4/cephcsi-rhel8 v4.12.3-3, odf4/odf-console-rhel8 v4.12.3-2, odf4/mcg-rhel8-operator v4.12.3-3, odf4/ocs-rhel8-operator v4.12.3-5, odf4/odf-rhel8-operator v4.12.3-3, odf4/odr-rhel8-operator v4.12.3-2, +16 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm jsonwebtoken
<9.0.0
9.0.0

Affected products

  • auth0 node-jsonwebtoken

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.