CVE-2017-11424

UnknownEPSS 1.80%

Last modified

CVE-2017-11424 is a vulnerability of currently unknown severity. In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. EPSS estimates a 1.80% chance of exploitation in the next 30 days.

Description

In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.

Metrics

EPSS Probability
1.80%

75.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
Pyjwt ProjectPyjwt<= 1.5.0
DebianDebian Linux8.0
DebianDebian Linux9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-11424?
In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.
How severe is CVE-2017-11424?
Severity scoring for CVE-2017-11424 is pending analysis. The EPSS model estimates a 1.80% probability of exploitation in the next 30 days.
How do I fix CVE-2017-11424?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-11424?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST