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 organizations 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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Zitadel | Zitadel | * | 2.54.10 (excluding) |
| Zitadel | Zitadel | 2.55.0 (including) | 2.55.8 (excluding) |
| Zitadel | Zitadel | 2.56.0 (including) | 2.56.6 (excluding) |
| Zitadel | Zitadel | 2.57.0 (including) | 2.57.5 (excluding) |
| Zitadel | Zitadel | 2.58.0 (including) | 2.58.5 (excluding) |
| Zitadel | Zitadel | 2.59.0 (including) | 2.59.3 (excluding) |
| Zitadel | Zitadel | 2.60.0 (including) | 2.60.2 (excluding) |
| Zitadel | Zitadel | 2.61.0 (including) | 2.61.0 (including) |
| Zitadel | Zitadel | 2.62.0 (including) | 2.62.0 (including) |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.