Zitadel up to 2.38.2/2.40.4 Lockout race condition

Summaryinfo

A vulnerability labeled as problematic has been found in Zitadel up to 2.38.2/2.40.4. Affected by this issue is some unknown functionality of the component Lockout. Executing a manipulation can lead to race condition. This vulnerability appears as CVE-2023-47111. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in Zitadel up to 2.38.2/2.40.4. This vulnerability affects an unknown part of the component Lockout. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The weakness was presented 11/09/2023 as GHSA-7h8m-vrxx-vr4m. The advisory is shared for download at github.com. This vulnerability was named CVE-2023-47111 since 10/30/2023. There are neither technical details nor an exploit publicly available.

Upgrading to version 2.38.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 22e2d5599918864877e054ebe82fb834a5aa1077 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Zitadel

Version

• 2.38.0
• 2.38.1
• 2.38.2
• 2.40.0
• 2.40.1
• 2.40.2
• 2.40.3
• 2.40.4

License

• open-source

Website

• Product: https://github.com/zitadel/zitadel/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion