CVE-2023-47111
published 2023-11-08CVE-2023-47111: ZITADEL provides identity infrastructure. ZITADEL provides administrators the possibility to define a `Lockout Policy` with a maximum amount of failed password…
PriorityP415low3.7CVSS 3.1
AVNACHPRNUINSUCNINAL
EPSS
0.52%
40.0th percentile
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
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | zitadel_zitadel | >= 0 < 2.38.3 | 2.38.3 |
| github.com | zitadel_zitadel | >= 2.39.0 < 2.40.5 | 2.40.5 |
| zitadel | zitadel | < 2.38.3 | 2.38.3 |
| zitadel | zitadel | — | — |
| zitadel | zitadel | >= 2.39.0 < 2.40.5 | 2.40.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
ZITADEL race condition in lockout policy execution
ghsa·2023-11-08
CVE-2023-47111 [HIGH] CWE-362 ZITADEL race condition in lockout policy execution
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](https://github.com/zitadel/zitadel/releases/tag/v2.40.5)
2.38.x versions are fixed on >= [2.38.3](https://github.com/zitadel/zitadel/releases/tag/v2.38.3)
### Worka
OSV
ZITADEL race condition in lockout policy execution
osv·2023-11-08
CVE-2023-47111 [HIGH] ZITADEL race condition in lockout policy execution
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](https://github.com/zitadel/zitadel/releases/tag/v2.40.5)
2.38.x versions are fixed on >= [2.38.3](https://github.com/zitadel/zitadel/releases/tag/v2.38.3)
### Worka
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077https://github.com/zitadel/zitadel/releases/tag/v2.38.3https://github.com/zitadel/zitadel/releases/tag/v2.40.5https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4mhttps://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077https://github.com/zitadel/zitadel/releases/tag/v2.38.3https://github.com/zitadel/zitadel/releases/tag/v2.40.5https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4m
2023-11-08
Published