ZITADEL vulnerable to Account Takeover with deactivated Instance IdP
zitadel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel Go |
|
|
zitadel
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel Go |
|
|
1.80.0-v2.20.0.20251112124840-33c51deb2040ZITADEL is an open source identity management platform. Starting in version 2.50.0 and prior to versions 2.71.19, 3.4.4, and 4.6.6, a vulnerability in ZITADEL's federation process allowed auto-linking users from external identity providers to existing users in ZITADEL even if the corresponding IdP was not active or if the organization did not allow federated authentication. This vulnerability stems from the platform's failure to correctly check or enforce an organization's specific security settings during the authentication flow. An Organization Administrator can explicitly disable an IdP or disallow federation, but this setting was not being honored during the auto-linking process. This allowed an unauthenticated attacker to initiate a login using an IdP that should have been disabled for that organization. The platform would incorrectly validate the login and, based on a matching criteria, link the attacker's external identity to an existing internal user account. This may result in a full Account Takeover, bypassing the organization's mandated security controls. Note that accounts with MFA enabled can not be taken over by this attack. Also note that only IdPs create on an instance level would allow this to work. IdPs registered on another organization would always be denied in the (auto-)linking process. Versions 4.6.6, 3.4.4, and 2.71.19 resolve the issue by correctly validating the organization's login policy before auto-linking an external user. No known workarounds are available aside from upgrading.
From the CVE record · GitHub_M
ZITADEL's federation auto-linking can ignore an organization's disabled identity provider or prohibition on federated authentication. An unauthenticated attacker can initiate a login through an instance-level identity provider and, if the linking criteria match, link their external identity to an existing account, potentially taking it over. Accounts with MFA enabled cannot be taken over this way; identity providers registered to another organization are denied.
Teams running ZITADEL or the Go package github.com/zitadel/zitadel in the affected ranges—2.50.0 to before 2.71.19, 3.0.0-rc.1 to before 3.4.4, 4.0.0-rc.1 to before 4.6.6, or 1.80.0-v2.20.0.20240403060621-5b3946b67ef6 to before 1.80.0-v2.20.0.20251112124840-33c51deb2040—should check.