Account Takeover via Session Fixation in Zitadel [Bypassing MFA]

Summary

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`.

Timeline

1. Mar 11, 2024, 7:48 PM UTCCVE published
2. Aug 26, 2024, 6:13 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Aug 26, 2024, 6:14 PM UTCRecord last updated

Affected versions

• zitadel zitadel

  fixed in 2.44.3; From 2.45.0 · fixed in 2.45.1

• github.com/zitadel/zitadelGo

  All versions

• github.com/zitadel/zitadelGo

  fixed in 2.44.3

• github.com/zitadel/zitadelGo

  From 2.45.0 · fixed in 2.45.1

References 1