ZITADEL: Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation)
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.4epss 0.3%
exploitation probability
0.3%top 80% of all CVEs
observed exploitation
nono source reports it
ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's OAuth2 and OIDC CodeExchange, RefreshToken, and device token flows fail to verify that the requesting client matches the client that initiated the authorization flow, allowing intercepted grants or refresh tokens to be exchanged under a different client. This issue is fixed in versions 3.4.12 and 4.15.2.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
zitadel · zitadelReferences
https://github.com/zitadel/zitadel/commit/562403079a98cf2059cdac11865a45e2f285be71https://github.com/zitadel/zitadel/commit/5b1708e0e650398f0ebc3341714f0798b0118917https://github.com/zitadel/zitadel/releases/tag/v3.4.12https://github.com/zitadel/zitadel/releases/tag/v4.15.2https://github.com/zitadel/zitadel/security/advisories/GHSA-xqxv-4jc2-x56x