User Grant 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 grants deactivation mechanism did not work correctly. Deactivated user grants were still provided in token, which could lead to unauthorized access to applications and resources. Additionally, the management and auth API always returned the state as active or did not provide any information about the state. 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 to upgrade. Users unable to upgrade may explicitly remove the user grants to make sure the user does not get access anymore.
From the CVE record · GitHub_M
ZITADEL can include deactivated user grants in tokens, potentially allowing access to applications and resources that should no longer be authorized. This occurs when user grants are deactivated; the input does not specify attacker authentication requirements or user interaction. The management and auth APIs can also report these grants as active or omit their state.
Operators of ZITADEL using affected github.com/zitadel/zitadel/v2 versions, or any version of github.com/zitadel/zitadel, should check their deployments.