DescriptionIn 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.
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
|National Vulnerability Database|
- openSUSE-SU-2017:2820-1, published Sat, 21 Oct 2017 00:11:00 +0200 (CEST)
List of released packages
|Product(s)||Fixed package version(s)||References|
|openSUSE Leap 42.3|| ||Patchnames:
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.
|CaaS Platform 1.0||python-PyJWT||Released|
|CaaS Platform 2.0||python-PyJWT||Released|
|OpenStack Cloud Magnum Orchestration 7.0||python-PyJWT||Released|
|SUSE Linux Enterprise Module for Public Cloud 12||python-PyJWT||Released|
|SUSE Openstack Cloud 7||python-PyJWT||Released|