CVE-2024-47060
Essential information
- Published
- 20/09/2024 00:15
- Modified
- 25/09/2024 16:43
- Author
- —
- Creator
- —
- CVSS
- 6.5 MEDIUM (v3.1)
- CISA KEV
- No
- CWE
- —
- CVSS vector
-
—
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N—
CVSS metrics
- Access vector
- —
- Access complexity
- —
- Authentication
- —
- Confidentiality impact
- —
- Integrity impact
- —
- Availability impact
- —
- Exploitability
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- NETWORK
- Attack complexity
- LOW
- Privileges required
- LOW
- User interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality impact
- HIGH
- Integrity impact
- NONE
- Availability impact
- NONE
- Exploit code maturity
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- —
- Attack complexity
- —
- Attack requirements
- —
- Privileges required
- —
- User interaction
- —
- Confidentiality (V)
- —
- Confidentiality (S)
- —
- Integrity (V)
- —
- Integrity (S)
- —
- Availability (V)
- —
- Availability (S)
- —
- Exploit maturity
- —
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.
NVD status
- Status
- Analyzed — CVE has been recently published to the CVE List and has been received by the NVD.
- Source
- [email protected]
- NVD
- View on NVD
Affected products (CPE)
| Product | CPE |
|---|---|
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:2.61.0:*:*:*:*:*:*:* |
| zitadel / zitadel | cpe:2.3:a:zitadel:zitadel:2.62.0:*:*:*:*:*:*:* |