CVE-2024-32868 json
ZITADEL's Improper Lockout Mechanism Leads to MFA Bypass
published 2y ago modified 2mo ago also EUVD-2024-1144 , GHSA-7j7j-66cv-m239 , GO-2024-2788
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
ZITADEL 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.
Patch / fix
- go github.com/zitadel/zitadel 2.50.0
- zitadel zitadel 2.50.0
Is CVE-2024-32868 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zitadel/zitadel | <2.50.0 all versions |
2.50.0 |
Affected products
- zitadel zitadel
Classification
References
-
github.com
/zitadel/zitadel/security/advisories/GHSA-7j7j-66cv-m239
web, vendor-advisory, advisory
-
github.com
/zitadel/zitadel/releases/tag/v2.50.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2024-32868
advisory
-
github.com
/zitadel/zitadel
package
Sources
- CVE List CVE-2024-32868
- GitHub Advisory GHSA-7j7j-66cv-m239
- NVD CVE-2024-32868
- OSV GO-2024-2788
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.