| Summary: | <dev-python/pyjwt-1.5.2: Incorrect handling of PEM-encoded public keys | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Agostino Sarubbo <ago> |
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | python |
| Priority: | Normal | Flags: | stable-bot:
sanity-check+
|
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1482529 | ||
| Whiteboard: | B3 [noglsa cve] | ||
| Package list: |
=dev-python/pyjwt-1.5.2
|
Runtime testing required: | No |
am64/x86 stable GLSA Vote: No |
From ${URL} : 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. Upstream bug: https://github.com/jpadilla/pyjwt/pull/277 @maintainer(s): since the fixed package is already in the tree, please let us know if it is ready for the stabilization or not.