CVE-2024-46999: User Grant Deactivation not Working in Zitadel

Published Sep 19, 2024
·
Updated

Impact

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.

Patches

2.x versions are fixed on >= 2.62.1 2.61.x versions are fixed on >= 2.61.1 2.60.x versions are fixed on >= 2.60.2 2.59.x versions are fixed on >= 2.59.3 2.58.x versions are fixed on >= 2.58.5 2.57.x versions are fixed on >= 2.57.5 2.56.x versions are fixed on >= 2.56.6 2.55.x versions are fixed on >= 2.55.8 2.54.x versions are fixed on >= 2.54.10

Workarounds

Unpatched versions can explicitly remove the user grants to make sure the user does not get access anymore.

Questions

If you have any questions or comments about this advisory, please email us at security@zitadel.com

Other sources

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.

— MITRE

Affected Software

18 affected componentsFixes available
go/github.com/zitadel/zitadel/v2<2.54.10
2.54.10
go/github.com/zitadel/zitadel/v2>=2.55.0<2.55.8
2.55.8
go/github.com/zitadel/zitadel/v2>=2.56.0<2.56.6
2.56.6
go/github.com/zitadel/zitadel/v2>=2.57.0<2.57.5
2.57.5
go/github.com/zitadel/zitadel/v2>=2.58.0<2.58.5
2.58.5
go/github.com/zitadel/zitadel/v2>=2.59.0<2.59.3
2.59.3
go/github.com/zitadel/zitadel/v2>=2.60.0<2.60.2
2.60.2
go/github.com/zitadel/zitadel/v2>=2.61.0<2.61.1
2.61.1
go/github.com/zitadel/zitadel/v2>=2.62.0<2.62.1
2.62.1
ZITADEL ZITADEL<2.54.10
ZITADEL ZITADEL>=2.55.0<2.55.8
ZITADEL ZITADEL>=2.56.0<2.56.6
ZITADEL ZITADEL>=2.57.0<2.57.5
ZITADEL ZITADEL>=2.58.0<2.58.5
ZITADEL ZITADEL>=2.59.0<2.59.3
ZITADEL ZITADEL>=2.60.0<2.60.2
ZITADEL ZITADEL=2.61.0
ZITADEL ZITADEL=2.62.0

Event History

Sep 19, 2024
Advisory Published
via GitHub·04:07 PM
CVE Published
via MITRE·11:11 PM
Data Sourced
via MITRE·11:11 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-46999?

CVE-2024-46999 is rated as a serious security vulnerability due to the potential for unauthorized access to applications and resources.

2

How do I fix CVE-2024-46999?

To fix CVE-2024-46999, upgrade to a secure version of ZITADEL, specifically 2.54.10 or later, or any of the versions 2.55.0 through 2.62.0.

3

What applications are affected by CVE-2024-46999?

CVE-2024-46999 affects ZITADEL versions up to 2.54.10 and versions from 2.55.0 to 2.62.0.

4

What happens if I don't address CVE-2024-46999?

If CVE-2024-46999 is not addressed, deactivated user grants may still allow unauthorized access to sensitive applications and resources.

5

Is CVE-2024-46999 exploit publicly available?

As of now, there is no public exploit available for CVE-2024-46999, but the risk associated with the vulnerability remains significant.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203