Service Users Deactivation not Working in Zitadel
zitadel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel/v2 Go |
|
zitadel
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel/v2 Go |
|
< 2.54.10
|
| github.com/zitadel/zitadel Go |
| No fix yet |
Zitadel is an open source identity management platform. ZITADEL's user account deactivation mechanism did not work correctly with service accounts. Deactivated service accounts retained the ability to request tokens, which could lead to unauthorized access to applications and resources. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised t upgrade. Users unable to upgrade may instead of deactivating the service account, consider creating new credentials and replacing the old ones wherever they are used. This effectively prevents the deactivated service account from being utilized. Be sure to revoke all existing authentication keys associated with the service account and to rotate the service account's password.
From the CVE record · GitHub_M
ZITADEL does not correctly deactivate service accounts. A deactivated service account can still request tokens, potentially allowing unauthorized access to applications and resources. The input does not specify authentication requirements or user interaction.
Check deployments using affected versions of Go package github.com/zitadel/zitadel/v2 (before the applicable fixed release from 2.54.10 through 2.62.1) or any version of github.com/zitadel/zitadel.