ZITADEL Allows IdP Intent Token Reuse
zitadel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel Go |
|
|
zitadel
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel Go |
|
|
The identity infrastructure software ZITADEL offers developers the ability to manage user sessions using the Session API. This API enables the use of IdPs for authentication, known as idp intents. Following a successful idp intent, the client receives an id and token on a predefined URI. These id and token can then be used to authenticate the user or their session. However, prior to versions 3.0.0, 2.71.9, and 2.70.10, it was possible to exploit this feature by repeatedly using intents. This allowed an attacker with access to the application’s URI to retrieve the id and token, enabling them to authenticate on behalf of the user. It's important to note that the use of additional factors (MFA) prevents a complete authentication process and, consequently, access to the ZITADEL API. Versions 3.0.0, 2.71.9, and 2.70.10 contain a fix for the issue. No known workarounds other than upgrading are available.
From the CVE record · GitHub_M
ZITADEL’s Session API allowed IdP intents to be reused after a successful authentication intent. An attacker with access to the application’s URI could retrieve the resulting ID and token and authenticate on behalf of the user; MFA prevents complete authentication and access to the ZITADEL API.
Teams running affected versions of ZITADEL or the Go package github.com/zitadel/zitadel before the fixes in their respective release lines should check their deployments.