Zitadel Bypass Second Authentication Factor
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.6.0, 3.4.3, 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- zitadel zitadel
From 4.0.0-rc.1 · fixed in 4.6.0; From 3.0.0-rc.1 · fixed in 3.4.3; From 2.55.0 · fixed in 2.71.18; From 2.54.3 · through 2.54.10; From 2.53.6 · through 2.53.9
- github.com/zitadel/zitadelGo
All versions
- github.com/zitadel/zitadel/v2Go
From 2.53.6 · through 2.53.9
- github.com/zitadel/zitadel/v2Go
From 2.54.3 · through 2.54.10
- github.com/zitadel/zitadel/v2Go
From 2.55.0 · fixed in 2.71.18
- github.com/zitadel/zitadelGo
fixed in 1.80.0-v2.20.0.20251029091250-b284f8474eed