CVE-2024-47060 — zitadel
MEDIUMCVE-2024-47060 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in github.com/zitadel/zitadel/v2. A fix is available for github.com/zitadel/zitadel/v2 — see the affected versions and patch details below.
Unauthorized Access After Organization or Project Deactivation in Zitadel
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47060.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 [email protected]
Credits
Thanks to @prdp1137 for reporting this!
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.62.0&&< 2.62.1 | 2.62.1go get github.com/zitadel/zitadel/v2@v2.62.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.61.0&&< 2.61.1 | 2.61.1go get github.com/zitadel/zitadel/v2@v2.61.1 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.60.0&&< 2.60.2 | 2.60.2go get github.com/zitadel/zitadel/v2@v2.60.2 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.59.0&&< 2.59.3 | 2.59.3go get github.com/zitadel/zitadel/v2@v2.59.3 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.58.0&&< 2.58.5 | 2.58.5go get github.com/zitadel/zitadel/v2@v2.58.5 |
| 🐹Go | github.com/zitadel/zitadel/v2 | ≥ 2.57.0&&< 2.57.5 | 2.57.5go get github.com/zitadel/zitadel/v2@v2.57.5 |
Affected Products
zitadelzitadelDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel/v2 to 2.62.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47060 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2024-47060 in your dependencies?
Find it across Go, including transitive dependencies.