CVE-2023-47111: ZITADEL race condition in lockout policy execution
Impact
ZITADEL provides administrators the possibility to define a Lockout Policy with a maximum amount of failed password check attempts. On every failed password check, the amount of failed checks is compared against the configured maximum. Exceeding the limit, will lock the user and prevent further authentication.
In the affected implementation it was possible for an attacker to start multiple parallel password checks, giving him the possibility to try out more combinations than configured in the Lockout Policy.
Patches
2.x versions are fixed on >= 2.40.5 2.38.x versions are fixed on >= 2.38.3
Workarounds
There is no workaround since a patch is already available.
References
None
Questions
If you have any questions or comments about this advisory, please email us at security@zitadel.com
Other sources
ZITADEL provides identity infrastructure. ZITADEL provides administrators the possibility to define a Lockout Policy with a maximum amount of failed password check attempts. On every failed password check, the amount of failed checks is compared against the configured maximum. Exceeding the limit, will lock the user and prevent further authentication. In the affected implementation it was possible for an attacker to start multiple parallel password checks, giving him the possibility to try out more combinations than configured in the Lockout Policy. This vulnerability has been patched in versions 2.40.5 and 2.38.3.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2023-47111?
CVE-2023-47111 is a vulnerability in ZITADEL that allows an attacker to lock a user's account by exceeding the maximum number of failed password attempts.
How severe is CVE-2023-47111?
CVE-2023-47111 has a severity level of 7.3 (high).
Which versions of ZITADEL are affected?
ZITADEL versions up to 2.38.3 and versions between 2.39.0 and 2.40.5 are affected by CVE-2023-47111.
How can I fix CVE-2023-47111?
To fix CVE-2023-47111, update ZITADEL to version 2.38.3 or upgrade to a version higher than 2.40.5.
Where can I find more information about CVE-2023-47111?
You can find more information about CVE-2023-47111 in the ZITADEL security advisory and the related GitHub commits and releases.