CVE-2023-47111
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 7.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Zitadel < 2.38.3
- Zitadel < 2.40.5
Attack profile CVSS 3.1 · 7.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-47111.md and follow it. Check whether this project is affected by CVE-2023-47111. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077
- https://github.com/zitadel/zitadel/releases/tag/v2.38.3
- https://github.com/zitadel/zitadel/releases/tag/v2.40.5
- https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4m
- https://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077
- https://github.com/zitadel/zitadel/releases/tag/v2.38.3
- https://github.com/zitadel/zitadel/releases/tag/v2.40.5
- https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4m
References
- https://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077
- https://github.com/zitadel/zitadel/releases/tag/v2.38.3
- https://github.com/zitadel/zitadel/releases/tag/v2.40.5
- https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4m
- https://github.com/zitadel/zitadel/commit/22e2d5599918864877e054ebe82fb834a5aa1077
- https://github.com/zitadel/zitadel/releases/tag/v2.38.3
- https://github.com/zitadel/zitadel/releases/tag/v2.40.5
- https://github.com/zitadel/zitadel/security/advisories/GHSA-7h8m-vrxx-vr4m