Upstream information
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.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having important severity.
| National Vulnerability Database | |
|---|---|
| Base Score | 5 |
| Vector | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
| National Vulnerability Database | |
|---|---|
| Base Score | 7.5 |
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | None |
| Integrity Impact | High |
| Availability Impact | None |
| CVSSv3 Version | 3 |
SUSE Security Advisories:
- openSUSE-SU-2017:2820-1
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise High Performance Computing 12 | python-PyJWT | Released |
| Products under Long Term Service Pack support and receiving important and critical security fixes. | ||
| SUSE Linux Enterprise Server 12 SP5 | python-PyJWT | Released |
| SUSE Linux Enterprise Server for SAP Applications 12 SP5 | python-PyJWT | Released |
| Products past their end of life and not receiving proactive updates anymore. | ||
| Magnum Orchestration 7 | python-PyJWT | Released |
| SUSE CaaS Platform 3.0 | python-PyJWT | Affected |
| SUSE Container as a Service Platform 1.0 | python-PyJWT | Released |
| SUSE Container as a Service Platform 2.0 | python-PyJWT | Released |
| SUSE Linux Enterprise Module for Public Cloud 12 | python-PyJWT | Released |
| SUSE Linux Enterprise Server 12 | python-PyJWT | Released |
| SUSE Linux Enterprise Server 12 SP3 | python-PyJWT | Released |
| SUSE Linux Enterprise Server 12 SP4 | python-PyJWT | Released |
| SUSE Linux Enterprise Server for SAP Applications 12 | python-PyJWT | Released |
| SUSE Linux Enterprise Server for SAP Applications 12 SP3 | python-PyJWT | Released |
| SUSE Linux Enterprise Server for SAP Applications 12 SP4 | python-PyJWT | Released |
| SUSE Manager Server 3.2 | python-PyJWT | Released |
| SUSE OpenStack Cloud 7 | python-PyJWT | Released |
SUSE Timeline for this CVE
CVE page created: Wed Aug 16 21:12:33 2017CVE page last modified: Fri Nov 1 12:13:57 2024