CVE-2024-28197: Account Takeover via Session Fixation in Zitadel [Bypassing MFA]
Impact 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.
Patches 2.x versions are fixed on >= 2.46.0 2.45.x versions are fixed on >= 2.45.1 2.44.x versions are fixed on >= 2.44.3
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.
Workarounds For self-hosted environments unable to upgrade to a patched version, prevent setting the following cookie name on subdomains of your ZITADEL instance (e.g. within your WAF): Secure-zitadel-useragent
References None
Questions If you have any questions or comments about this advisory, please email us at security@zitadel.com
Credits Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
Other sources
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 setting the following cookie name on subdomains of your Zitadel instance (e.g. within your WAF): Secure-zitadel-useragent.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-28197?
CVE-2024-28197 is classified as a medium severity vulnerability that affects user session management.
How do I fix CVE-2024-28197?
To mitigate CVE-2024-28197, upgrade ZITADEL to version 2.45.1 or later.
What types of systems are affected by CVE-2024-28197?
CVE-2024-28197 affects all versions of ZITADEL prior to 2.45.1.
Can CVE-2024-28197 lead to session hijacking?
Yes, CVE-2024-28197 could potentially allow attackers to hijack user sessions through accessible cookies.
What is the impact of exploiting CVE-2024-28197?
Exploitation of CVE-2024-28197 could enable an attacker to access sensitive user data and manipulate user sessions.