Skip to content

ZITADEL race condition in lockout policy execution

High severity GitHub Reviewed Published Nov 8, 2023 in zitadel/zitadel • Updated Nov 9, 2023

Package

gomod github.com/zitadel/zitadel (Go)

Affected versions

>= 2.39.0, < 2.40.5
< 2.38.3

Patched versions

2.40.5
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]

References

@livio-a livio-a published to zitadel/zitadel Nov 8, 2023
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

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.083%
(37th percentile)

Weaknesses

CVE ID

CVE-2023-47111

GHSA ID

GHSA-7h8m-vrxx-vr4m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.