CVE-2024-32868
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZITADEL provides users the possibility to use Time-based One-Time-Password (TOTP) and One-Time-Password (OTP) through SMS and Email. While ZITADEL already gives administrators the option to define a `Lockout Policy` with a maximum amount of failed password check attempts, there was no such mechanism for (T)OTP checks. This issue has been patched in version 2.50.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceZITADEL lacked rate limiting or account lockout for TOTP/OTP authentication attempts, unlike password-based authentication which had a configurable Lockout Policy. This allowed unlimited brute-force attempts on (T)OTP codes without triggering any account lockout, enabling attackers to systematically guess valid codes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.50.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed ZITADEL versionLocate the ZITADEL version information in the system (typically available via admin console, /version API endpoint, or container/service metadata)Affected if The installed version is below 2.50.0
-
Verify TOTP/OTP authentication is enabledCheck ZITADEL authentication configuration to confirm that Time-based One-Time Password (TOTP) or One-Time Password (OTP) methods are configured as allowed authentication mechanisms for users or applicationsAffected if TOTP/OTP authentication methods are enabled in the ZITADEL instance
-
Review existing lockout policy configurationAccess the ZITADEL admin console or policy settings and examine the Password Lockout Policy settings (typically found under Authentication Policies or Security Policies)Affected if A Lockout Policy exists for password authentication but does not include or reference TOTP/OTP attempt limitations
-
Confirm no rate limiting exists for OTP endpointsInspect API gateway or ZITADEL rate limiting configuration to verify whether there are any rate limits or attempt restrictions applied specifically to OTP/TOTP authentication endpointsAffected if No rate limiting or attempt throttling is configured for OTP/TOTP authentication endpoints
A ZITADEL instance is affected if it runs version below 2.50.0 and has TOTP/OTP authentication enabled without any lockout policy or rate limiting applied to those authentication attempts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.50.0
Upgrade ZITADEL to version 2.50.0 or later which implements the missing lockout mechanism for (T)OTP authentication attempts.
Zitadel version 2.50.0 or later
- Backup your Zitadel database and configuration before upgrading
- Identify your current Zitadel version (check via admin console or API)
- Upgrade your Zitadel instance to version 2.50.0 or later
- After upgrading, verify that the TOTP/OTP lockout policy is now available in the admin console under authentication policies
- Configure the appropriate failed attempt threshold for (T)OTP verifications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data