CVE-2017-11424
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
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Pyjwt Project | Pyjwt | <= 1.5.0 |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
References
- http://www.debian.org/security/2017/dsa-3979Third Party Advisory
- https://github.com/jpadilla/pyjwt/pull/277Issue Tracking, Patch, Third Party Advisory
- http://www.debian.org/security/2017/dsa-3979Third Party Advisory
- https://github.com/jpadilla/pyjwt/pull/277Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-11424?
How severe is CVE-2017-11424?
How do I fix CVE-2017-11424?
Are you affected by CVE-2017-11424?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
