Vulnerability record · CVE-2017-11424 · published 24 August 2017
CVE-2017-11424: Pyjwt project pyjwt vulnerability
Pyjwt Project · Pyjwt
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.
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.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.debian.org/security/2017/dsa-3979 | Third Party Advisory |
| https://github.com/jpadilla/pyjwt/pull/277 | Issue TrackingPatchThird Party Advisory |
| http://www.debian.org/security/2017/dsa-3979 | Third Party Advisory |
| https://github.com/jpadilla/pyjwt/pull/277 | Issue TrackingPatchThird Party Advisory |
Track CVE-2017-11424 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2017-11424), CISA KEV, FIRST EPSS (scores of 2026-09-29). This page is refreshed as NVD updates the record.