PyJWT
PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion
PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.1.0, < 2.15.0
Fixed in 2.15.0
Mitigation
Upgrade pyjwt to 2.15.0 or later.
References
- Vendor advisory github.com/jpadilla/pyjwt/security/advisories/…
- Patch github.com/jpadilla/pyjwt/commit/3cd9ceec33ced…
- Release notes github.com/jpadilla/pyjwt/releases/tag/2.15.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.