CVE-2022-292177.4HighCWE-327

CVE-2022-29217: Key confusion through non-blocklisted public key formats in PyJWT

jpadilla · pyjwt

Vendor fix available · Affected: jpadilla pyjwt · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.4%probability of exploitation in the next 30 days

72nd percentile

050100

Higher than 72% of scored CVEs

7.4HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify `jwt.algorithms.get_default_algorithms()` to get support for all algorithms, or specify a single algorithm. The issue is not that big as `algorithms=jwt.algorithms.get_default_algorithms()` has to be used. Users should upgrade to v2.4.0 to receive a patch for this issue. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

jpadilla · pyjwt>= 1.5.0, < 2.4.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of a Broken or Risky Cryptographic Algorithm · Cryptography
Vendor: jpadilla
Published: May 2022
Band: Possible (1 to 10%), May 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-29217 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.