| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| github.com/zitadel/zitadel | 全バージョン | |
| github.com/zitadel/zitadel/v2 | ≥ 2.55.0, < 2.55.8≥ 2.56.0, < 2.56.6≥ 2.57.0, < 2.57.5≥ 2.58.0, < 2.58.5≥ 2.59.0, < 2.59.3≥ 2.60.0, < 2.60.2≥ 2.61.0, < 2.61.1≥ 2.62.0, < 2.62.1< 2.54.10 | 2.55.82.56.62.57.52.58.52.59.32.60.22.61.12.62.12.54.10 |
| zitadel | = 2.61.0= 2.62.0≥ 2.55.0, < 2.55.8≥ 2.56.0, < 2.56.6≥ 2.57.0, < 2.57.5≥ 2.58.0, < 2.58.5≥ 2.59.0, < 2.59.3≥ 2.60.0, < 2.60.2< 2.54.10 | 2.55.82.56.62.57.52.58.52.59.32.60.22.54.10 |
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.
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
Unpatched versions can explicitly disable the application to make sure the client is not allowed anymore.
If you have any questions or comments about this advisory, please email us at
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャンThanks to @prdp1137 for reporting this!