GitHub Advisoryadvisory · Go

GHSA-7h8m-vrxx-vr4m ZITADEL race condition in lockout policy execution

HIGH Published 2023-11-08 Modified 2023-11-09 Official page ↗
Aliases
CVE-2023-47111
Ecosystem
Go
Packages
github.com/zitadel/zitadel
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses
CWE-362
Reviewed
2023-11-08

Affected packages

• Go github.com/zitadel/zitadel: >= 2.39.0, < 2.40.5 → fixed in 2.40.5 • Go github.com/zitadel/zitadel: < 2.38.3 → fixed in 2.38.3

Description

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 [email protected]

Related

Alias · CVE (1)

  • CVE-2023-47111 ZITADEL provides identity infrastructure. vulnerability

Weakness · CWE (1)

  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness

References