PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

• PyJWT 2.15.0Fixed version · GitHub Advisories · pip package PyJWT: upgrade to 2.15.0 or later (affected >= 2.1.0, <= 2.14.0)
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Packages ]Affected open-source packages

• PyJWT pipAffected >= 2.1.0, <= 2.14.0 · fixed in 2.15.0 · GHSA-x33g-cr3x-6449

[ References ]References

• github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332cPatch
• github.com/jpadilla/pyjwt/releases/tag/2.15.0ProductRelease Notes
• github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449ExploitVendor Advisory