CVE-2017-11424

NONE
Published Aug 24, 20178y ago · Modified Jun 17, 20261w ago
Find Similar
Published Aug 24, 2017 8y ago
Last Modified Jun 17, 2026 1w ago

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.

Threat Intelligence

No active exploitation signals — not in CISA KEV and no EPSS score yet.

Exploit & Patch Status
No Known Exploit
Patch Available

Affected Products 3

VendorProductVersionRange
pyjwt_projectpyjwt* ≤1.5.0
debiandebian_linux8.0any
debiandebian_linux9.0any

References 2

  • debian.org http://www.debian.org/security/2017/dsa-3979
    Third Party Advisory
  • github.com https://github.com/jpadilla/pyjwt/pull/277
    Issue TrackingPatchThird Party Advisory

Remediation

  • github.com https://github.com/jpadilla/pyjwt/pull/277
    Issue TrackingPatchThird Party Advisory