| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/zitadel/zitadel | ≥ 0.0.0-20230609131415-dafa8ab4dfe8, < 0.0.0-20240731122357-a1d24353db4d≥ 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8, < 1.80.0-v2.20.0.20240731122357-a1d24353db4d≥ 2.53.0, < 2.53.9≥ 2.54.0, < 2.54.8≥ 2.55.0, < 2.55.5≥ 2.56.0, < 2.56.2≥ 2.57.0, < 2.57.1≥ 2.58.0, < 2.58.1all versions | 0.0.0-20240731122357-a1d24353db4d1.80.0-v2.20.0.20240731122357-a1d24353db4d2.53.92.54.82.55.52.56.22.57.12.58.1 |
| zitadel | = 2.57.0= 2.58.0≥ 2.53.0, < 2.53.9≥ 2.54.0, < 2.54.8≥ 2.55.0, < 2.55.5≥ 2.56.0, < 2.56.2 | 2.53.92.54.82.55.52.56.2 |
ZITADEL administrators can enable a setting called "Ignoring unknown usernames" which helps mitigate attacks that try to guess/enumerate usernames. If enabled, ZITADEL will show the password prompt even if the user doesn't exist and report "Username or Password invalid". Due to a implementation change to prevent deadlocks calling the database, the flag would not be correctly respected in all cases and an attacker would gain information if an account exist within ZITADEL, since the error message shows "object not found" instead of the generic error message.
2.x versions are fixed on >= 2.58.1 2.57.x versions are fixed on >= 2.57.1 2.56.x versions are fixed on >= 2.56.2 2.55.x versions are fixed on >= 2.55.5 2.54.x versions are fixed on >= 2.54.8 2.53.x versions are fixed on >= 2.53.9
ZITADEL recommends upgrading to the latest versions available in due course.
There is no workaround since a patch is already available.
If you have any questions or comments about this advisory, please email us at [email protected]
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free