Zitadel Bypass Second Authentication Factor
zitadel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel/v2 Go |
|
|
| github.com/zitadel/zitadel Go |
|
zitadel
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zitadel/zitadel/v2 Go |
|
|
| github.com/zitadel/zitadel Go |
|
|
Starting from 2.53.6, 2.54.3, and 2.55.0, Zitadel only required multi factor authentication in case the login policy has either enabled requireMFA or requireMFAForLocalUsers. If a user has set up MFA without this requirement, Zitadel would consider single factor auhtenticated sessions as valid as well and not require multiple factors. Bypassing second authentication factors weakens multifactor authentication and enables attackers to bypass the more secure factor. An attacker can target the TOTP code alone, only six digits, bypassing password verification entirely and potentially compromising accounts with 2FA enabled. This vulnerability is fixed in 4.6.0, 3.4.3, and 2.71.18.
From the CVE record · GitHub_M
In affected Zitadel versions, users who set up MFA may still have single-factor sessions accepted if the login policy does not enable requireMFA or requireMFAForLocalUsers. An attacker can target the six-digit TOTP code alone, bypassing password verification and potentially compromising accounts with 2FA enabled.
Check Zitadel installations and Go packages github.com/zitadel/zitadel/v2 (2.53.6–2.53.9, 2.54.3–2.54.10, or 2.55.0 before 2.71.18) and github.com/zitadel/zitadel (versions before 1.80.0-v2.20.0.20251029091250-b284f8474eed).