CVE-2024-47060: Unauthorized Access After Organization or Project Deactivation in Zitadel
Summary In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible.
Details The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible.
PoC - Create a new Organization, create new project and setup OpenID connect. - Deactivate an Organization - Setup authentication without selecting Check for Project on Authentication - User is able to login despite the organization is deactivated
Impact This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation.
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
Workaround Unpatched versions can explicitly disable the application to make sure the client is not allowed anymore.
Questions If you have any questions or comments about this advisory, please email us at security@zitadel.com
Credits Thanks to @prdp1137 for reporting this!
Other sources
Zitadel is an open source identity management platform. In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible. The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. 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 disable the application to make sure the client is not allowed anymore.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47060?
The severity of CVE-2024-47060 is categorized as high due to potential unauthorized access to applications after organization deactivation.
How do I fix CVE-2024-47060?
To fix CVE-2024-47060, upgrade Zitadel to versions 2.54.11, 2.55.8, 2.56.6, 2.57.5, 2.58.5, 2.59.3, 2.60.2, 2.61.1, or 2.62.1.
What impact does CVE-2024-47060 have on user security?
CVE-2024-47060 can lead to unauthorized access by allowing users from other organizations to log in to still active applications.
Which Zitadel versions are vulnerable to CVE-2024-47060?
Zitadel versions prior to 2.54.10 and those between 2.55.0 and 2.62.0, including 2.61.0 are vulnerable to CVE-2024-47060.
Is there a way to mitigate CVE-2024-47060 without updating?
There are no recommended mitigations for CVE-2024-47060 other than upgrading to a safe version.