NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2024-47060: ZITADEL Allows Unauthorized Access After Organization or Project Deactivation

highCVSS 4.0 7.4 · 3.1 6.8GHSA-jj94-6f5c-65r8

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.

Published Sep 19, 2024 · Updated Nov 18, 2024

Affected packages

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.62.0, < 2.62.1
Fixed in
2.62.1
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.61.0, < 2.61.1
Fixed in
2.61.1
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.60.0, < 2.60.2
Fixed in
2.60.2
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.59.0, < 2.59.3
Fixed in
2.59.3
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.58.0, < 2.58.5
Fixed in
2.58.5
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.57.0, < 2.57.5
Fixed in
2.57.5
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.56.0, < 2.56.6
Fixed in
2.56.6
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
>= 2.55.0, < 2.55.8
Fixed in
2.55.8
Check
go list -m github.com/zitadel/zitadel/v2

github.com/zitadel/zitadel/v2

Ecosystem
Go
Affected
< 2.54.10
Fixed in
2.54.10
Check
go list -m github.com/zitadel/zitadel/v2

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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]](mailto:[email protected])

Credits

Thanks to @prdp1137 for reporting this!

Credited to prdp1137, livio-a, fforootd.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries