CVE-2024-47060 Unauthorized Access After Organization or Project Deactivation in Zitadel

Medium 4.3 Published Updated

Attackers can access deactivated organization projects and applications, leading to unauthorized data exposure and security bypass in Zitadel.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2024-47060?

CVE-2024-47060 is a medium-severity missing authorization vulnerability in zitadel, published on 19 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-863, CWE-200

Which versions are affected by CVE-2024-47060?

19 open source packages ship an affected version, including github.com/zitadel/zitadel/v2 and github.com/zitadel/zitadel. It affects 1 product.

PackageAffectedFixed in
github.com/zitadel/zitadel/v2 GoAll versions2.54.10
github.com/zitadel/zitadel/v2 GoAll versions2.54.10
github.com/zitadel/zitadel/v2 GoFrom 2.55.02.55.8
github.com/zitadel/zitadel/v2 GoFrom 2.55.02.55.8
github.com/zitadel/zitadel/v2 GoFrom 2.56.02.56.6
github.com/zitadel/zitadel/v2 GoFrom 2.56.02.56.6
13 more packages
github.com/zitadel/zitadel/v2 GoFrom 2.57.02.57.5
github.com/zitadel/zitadel/v2 GoFrom 2.57.02.57.5
github.com/zitadel/zitadel/v2 GoFrom 2.58.02.58.5
github.com/zitadel/zitadel/v2 GoFrom 2.58.02.58.5
github.com/zitadel/zitadel/v2 GoFrom 2.59.02.59.3
github.com/zitadel/zitadel/v2 GoFrom 2.59.02.59.3
github.com/zitadel/zitadel/v2 GoFrom 2.60.02.60.2
github.com/zitadel/zitadel/v2 GoFrom 2.60.02.60.2
github.com/zitadel/zitadel/v2 GoFrom 2.61.02.61.1
github.com/zitadel/zitadel/v2 GoFrom 2.61.02.61.1
github.com/zitadel/zitadel/v2 GoFrom 2.62.02.62.1
github.com/zitadel/zitadel/v2 GoFrom 2.62.02.62.1
github.com/zitadel/zitadel GoAll versionsNone

Products include Zitadel Zitadel.

How do I fix CVE-2024-47060?

Upgrade github.com/zitadel/zitadel/v2 to a fixed version for your release line: 2.54.10, 2.55.8, 2.56.6 or 2.57.5.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2024-47060 being exploited?

There is no known exploitation of CVE-2024-47060 in the wild and no public exploit code.

Sources

Also known as GHSA-jj94-6f5c-65r8, GO-2024-3138.

Is CVE-2024-47060 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free