python-jwt: Incorrect handling of PEM-encoded public keys
Published Aug 24, 2017
7.5
HIGHCVSS 3.0
EPSS 1.80%
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.
Affected products
No data.
Configuration 1
- ≤ 1.5.0
Configuration 2
- 8.0
- 9.0
No data.
Red Hat Enterprise Linux 7
python-jwt
Not affected
Red Hat Storage 3
python-jwt
Will not fix
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | python-jwt | Not affected | n/a |
| Red Hat Storage 3 | python-jwt | Will not fix | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
1 other source (Red Hat) ▾
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
AV:N/AC:L/Au:N/C:N/I:P/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 3, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (17 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 3, 2026 | 1.80% (0.01804) | 77.79th | v5 (v2026.06.15) |
| Jun 15, 2026 | 1.79% (0.01789) | 75.41th | v5 (v2026.06.15) |
| Apr 26, 2026 | 0.19% (0.00193) | 41.02th | v4 (v2025.03.14) |
| Mar 30, 2025 | 1.30% (0.01296) | 77.86th | v4 (v2025.03.14) |
| Mar 29, 2025 | 12.71% (0.12714) | 89.96th | v4 (v2025.03.14) |
| Jul 20, 2024 | 0.08% (0.00082) | 35.48th | v3 (v2023.03.01) |
| Nov 28, 2023 | 0.08% (0.00082) | 34.30th | v3 (v2023.03.01) |
| May 8, 2023 | 0.11% (0.00115) | 43.83th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.14% (0.00136) | 47.22th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Sep 10, 2022 | 0.89% (0.00885) | 26.24th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.89% (0.00885) | 24.24th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.89% (0.00885) | 10.50th | v2 (v2022.01.01) |
| Feb 3, 2022 | 0.62% (0.00624) | 17.80th | v1 |
| Jan 6, 2022 | 0.62% (0.00624) | 17.24th | v1 |
| Sep 1, 2021 | 0.62% (0.00624) | 45.04th | v1 |
| Apr 14, 2021 | 0.62% (0.00624) | 0.00th | v1 |
No CWE recorded.
References (8)
- http://www.debian.org/security/2017/dsa-3979 vendor-advisoryx_refsource_DEBIANThird Party Advisory
- https://access.redhat.com/security/cve/CVE-2017-11424 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1482529 Issue Tracking
- https://github.com/advisories/GHSA-r9jw-mwhq-wp62 Advisory
- https://github.com/jpadilla/pyjwt/pull/277 x_refsource_CONFIRMIssue TrackingPatchThird Party Advisory
- https://github.com/pypa/advisory-database/tree/main/vulns/pyjwt/PYSEC-2017-24.yaml
- https://nvd.nist.gov/vuln/detail/CVE-2017-11424
- https://www.cve.org/CVERecord?id=CVE-2017-11424
| Link | Providers | Tags |
|---|---|---|
| http://www.debian.org/security/2017/dsa-3979 | vendor-advisoryx_refsource_DEBIANThird Party Advisory | |
| https://access.redhat.com/security/cve/CVE-2017-11424 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1482529 | Issue Tracking | |
| https://github.com/advisories/GHSA-r9jw-mwhq-wp62 | Advisory | |
| https://github.com/jpadilla/pyjwt/pull/277 | x_refsource_CONFIRMIssue TrackingPatchThird Party Advisory | |
| https://github.com/pypa/advisory-database/tree/main/vulns/pyjwt/PYSEC-2017-24.yaml | ||
| https://nvd.nist.gov/vuln/detail/CVE-2017-11424 | ||
| https://www.cve.org/CVERecord?id=CVE-2017-11424 |
Change history (0)
No recorded changes yet.