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.
References
Link | Resource |
---|---|
http://www.debian.org/security/2017/dsa-3979 | Third Party Advisory |
https://github.com/jpadilla/pyjwt/pull/277 | Issue Tracking Patch Third Party Advisory |
http://www.debian.org/security/2017/dsa-3979 | Third Party Advisory |
https://github.com/jpadilla/pyjwt/pull/277 | Issue Tracking Patch Third Party Advisory |
Configurations
History
21 Nov 2024, 03:07
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.debian.org/security/2017/dsa-3979 - Third Party Advisory | |
References | () https://github.com/jpadilla/pyjwt/pull/277 - Issue Tracking, Patch, Third Party Advisory |
Information
Published : 2017-08-24 16:29
Updated : 2024-11-21 03:07
NVD link : CVE-2017-11424
Mitre link : CVE-2017-11424
CVE.ORG link : CVE-2017-11424
JSON object : View
Products Affected
debian
- debian_linux
pyjwt_project
- pyjwt
CWE