Lockout bypass via stale concurrent password-check state
Published Nov 8, 2023 · Updated Sep 12, 2024
Race condition in ZITADEL before 2.38.3 and 2.39.0 through 2.40.4 allows remote attackers to exceed password-attempt limits. HumanCheckPassword verifies a password before refreshing its event-backed write model, so concurrent checks can each evaluate stale failure and lock state. A known username and parallel password attempts are required; the bypass permits extra guesses before the configured account lockout takes effect.
Summary
What happened
Race condition in ZITADEL before 2.38.3 and 2.39.0 through 2.40.4 allows remote attackers to exceed password-attempt limits. HumanCheckPassword verifies a password before refreshing its event-backed write model, so concurrent checks can each evaluate stale failure and lock state. A known username and parallel password attempts are required; the bypass permits extra guesses before the configured account lockout takes effect.
The record
- CVE
- CVE-2023-47111
- Published
- Nov 8, 2023
- Updated
- Sep 12, 2024
- Vendor
- ZITADEL
- Product
- ZITADEL
- Classifications
- CWE-362, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.38.3
- Affected versionversion=>= 2.39.0, < 2.40.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo