ZITADEL race condition in lockout policy execution
Package
Affected versions
>= 2.39.0, < 2.40.5
< 2.38.3
Patched versions
2.40.5
2.38.3
Description
Published to the GitHub Advisory Database
Nov 8, 2023
Reviewed
Nov 8, 2023
Published by the National Vulnerability Database
Nov 8, 2023
Last updated
Nov 9, 2023
Impact
ZITADEL provides administrators the possibility to define a
Lockout Policywith 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
References