CVE intelligence and bounded remediation
CVE-2024-28197 — Zitadel is an open source identity management system
Zitadel is an open source identity management system. Zitadel uses a cookie to identify the user agent (browser) and its user sessions. Although the cookie was handled according to best practices, it was accessible on subdomains of the ZITADEL instance. An attacker could take advantage of this and provide a malicious link hosted on the subdomain to the user to gain access to the victim’s account in certain scenarios. A possible victim would need to login through the malicious link for this exploit to work. If the possible victim already had the cookie present, the attack would not succeed. The attack would further only be possible if there was an initial vulnerability on the subdomain. This could either be the attacker being able to control DNS or a XSS vulnerability in an application hosted on a subdomain. Versions 2.46.0, 2.45.1, and 2.44.3 have been patched. Zitadel recommends upgrading to the latest versions available in due course. Note that applying the patch will invalidate the current cookie and thus users will need to start a new session and existing sessions (user selection) will be empty. For self-hosted environments unable to upgrade to a patched version, prevent setti…
- Severity
- High
- CVSS
- 7.5 (3.1)
- Published
- 2024-03-11
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-269, CWE-384
Affected products
- zitadel / zitadel
- zitadel / zitadel / 2.45.0
- zitadel / zitadel / 2.46.0
Matched remediation archetype
Privilege escalation and unsafe privilege management
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
- Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
- Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.
Remediate safely
- Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
- Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
- Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.