What is GHSA-567v-6hmg-6qg7?

GHSA-567v-6hmg-6qg7 is a security advisory published by GitHub Security Advisories with Medium severity. ZITADEL "ignoring unknown usernames" vulnerability

Which CVE IDs does GHSA-567v-6hmg-6qg7 cover?

GHSA-567v-6hmg-6qg7 covers the following CVE IDs: CVE-2024-41952. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-567v-6hmg-6qg7?

GHSA-567v-6hmg-6qg7 has a CVSS v3 base score of 5.3, published by GitHub Security Advisories.

Which products are affected by GHSA-567v-6hmg-6qg7?

GHSA-567v-6hmg-6qg7 affects 8 products, including: go/github.com/zitadel/zitadel:\u003e= 2.53.0, \u003c= 2.53.8; go/github.com/zitadel/zitadel:\u003e= 2.54.0, \u003c= 2.54.7; go/github.com/zitadel/zitadel:\u003e= 2.55.0, \u003c= 2.55.4; go/github.com/zitadel/zitadel:\u003e= 2.56.0, \u003c= 2.56.1; go/github.com/zitadel/zitadel:= 2.57.0; and others — see the full list on the advisory page.

GHSA-567v-6hmg-6qg7MediumCVSS 5.3

ZITADEL "ignoring unknown usernames" vulnerability

Vendor

GitHub Security Advisories

Published

July 31, 2024

Last Modified

July 8, 2025

🔗 CVE IDs covered (1)

CVE-2024-41952 →

📋 Description

Impact

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.

Patches

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.

Workarounds

There is no workaround since a patch is already available.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

🎯 Affected products8

go/github.com/zitadel/zitadel:>= 2.53.0, <= 2.53.8
go/github.com/zitadel/zitadel:>= 2.54.0, <= 2.54.7
go/github.com/zitadel/zitadel:>= 2.55.0, <= 2.55.4
go/github.com/zitadel/zitadel:>= 2.56.0, <= 2.56.1
go/github.com/zitadel/zitadel:= 2.57.0
go/github.com/zitadel/zitadel:= 2.58.0
go/github.com/zitadel/zitadel:>= 0.0.0-20230609131415-dafa8ab4dfe8, < 0.0.0-20240731122357-a1d24353db4d
go/github.com/zitadel/zitadel:>= 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8, < 1.80.0-v2.20.0.20240731122357-a1d24353db4d