PyJWT
PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation
PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.1critical · scored by NVD · CWE-347
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
jpadilla pyjwt
- >= 2.13.0, < 2.14.0
Fixed in 2.14.0
Mitigation
Upgrade pyjwt to 2.14.0 or later.
References
- Vendor advisory github.com/jpadilla/pyjwt/security/advisories/…
- Patch github.com/jpadilla/pyjwt/commit/f91ed44dd65ba…
- Release notes github.com/jpadilla/pyjwt/releases/tag/2.14.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.