ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.2epss 0.2%
exploitation probability
0.2%top 94% 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 is an open source identity management platform. From 3.0.0-rc.1 through 3.4.11 and from 4.0.0-rc.1 through 4.15.1, ZITADEL's external JWT Identity Provider validation in internal/idp/providers/jwt/session.go skips expiration handling when an incoming token omits the exp claim, allowing a token from a trusted issuer to be treated as valid without an automatic expiration window. This issue is fixed in versions 3.4.12 and 4.15.2.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Affected products
zitadel · zitadelReferences
https://github.com/zitadel/zitadel/commit/4925fab849d39a88674485d937b79e54318b48a8https://github.com/zitadel/zitadel/commit/d1c3aa84af8fcb0f33910ada30b866f4afb551achttps://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-v77h-2w3m-94hx