# CVE-2024-41952: Zitadel has an "Ignoring unknown usernames" vulnerability > Attackers can enumerate valid usernames in Zitadel when the 'Ignoring unknown usernames' setting is enabled, bypassing the intended security mitigation. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 31 Jul 2024 - **Updated:** 31 Jul 2024 - **Also known as:** GHSA-567v-6hmg-6qg7, GO-2024-3014 ## What is CVE-2024-41952? CVE-2024-41952 is a medium-severity vulnerability in zitadel, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Zitadel is an open source identity management system. 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. This vulnerability is fixed in 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8, and 2.53.9. Weakness: CWE-203 (Observable Discrepancy) ## Which versions are affected by CVE-2024-41952? 17 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel` | Go | All versions | None | | `github.com/zitadel/zitadel` | Go | From 0.0.0-20230609131415-dafa8ab4dfe8 | 0.0.0-20240731122357-a1d24353db4d | | `github.com/zitadel/zitadel` | Go | From 0.0.0-20230609131415-dafa8ab4dfe8 | 0.0.0-20240731122357-a1d24353db4d | | `github.com/zitadel/zitadel` | Go | From 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8 | 1.80.0-v2.20.0.20240731122357-a1d24353db4d | | `github.com/zitadel/zitadel` | Go | From 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8 | 1.80.0-v2.20.0.20240731122357-a1d24353db4d | | `github.com/zitadel/zitadel` | Go | From 2.53.0 | 2.53.9 | | `github.com/zitadel/zitadel` | Go | From 2.53.0 | 2.53.9 | | `github.com/zitadel/zitadel` | Go | From 2.54.0 | 2.54.8 | | `github.com/zitadel/zitadel` | Go | From 2.54.0 | 2.54.8 | | `github.com/zitadel/zitadel` | Go | From 2.55.0 | 2.55.5 | | `github.com/zitadel/zitadel` | Go | From 2.55.0 | 2.55.5 | | `github.com/zitadel/zitadel` | Go | From 2.56.0 | 2.56.2 | | `github.com/zitadel/zitadel` | Go | From 2.56.0 | 2.56.2 | | `github.com/zitadel/zitadel` | Go | From 2.57.0 | 2.57.1 | | `github.com/zitadel/zitadel` | Go | From 2.57.0 | 2.57.1 | | `github.com/zitadel/zitadel` | Go | From 2.58.0 | 2.58.1 | | `github.com/zitadel/zitadel` | Go | From 2.58.0 | 2.58.1 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-41952? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 0.0.0-20240731122357-a1d24353db4d, 1.80.0-v2.20.0.20240731122357-a1d24353db4d, 2.53.9 or 2.54.8. ## Is CVE-2024-41952 being exploited? There is no known exploitation of CVE-2024-41952 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-41952 and fix it if it is affected. What it is: CVE-2024-41952 is a medium-severity vulnerability in zitadel, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-41952 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel (Go): affected all versions; no fix listed - github.com/zitadel/zitadel (Go): affected from 0.0.0-20230609131415-dafa8ab4dfe8; fixed in 0.0.0-20240731122357-a1d24353db4d - github.com/zitadel/zitadel (Go): affected from 0.0.0-20230609131415-dafa8ab4dfe8; fixed in 0.0.0-20240731122357-a1d24353db4d - github.com/zitadel/zitadel (Go): affected from 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8; fixed in 1.80.0-v2.20.0.20240731122357-a1d24353db4d - github.com/zitadel/zitadel (Go): affected from 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8; fixed in 1.80.0-v2.20.0.20240731122357-a1d24353db4d - github.com/zitadel/zitadel (Go): affected from 2.53.0; fixed in 2.53.9 - github.com/zitadel/zitadel (Go): affected from 2.53.0; fixed in 2.53.9 - github.com/zitadel/zitadel (Go): affected from 2.54.0; fixed in 2.54.8 - github.com/zitadel/zitadel (Go): affected from 2.54.0; fixed in 2.54.8 - github.com/zitadel/zitadel (Go): affected from 2.55.0; fixed in 2.55.5 - github.com/zitadel/zitadel (Go): affected from 2.55.0; fixed in 2.55.5 - github.com/zitadel/zitadel (Go): affected from 2.56.0; fixed in 2.56.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-41952/ (Markdown: https://insights.sbomify.com/CVE-2024-41952/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41952 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41952 - OSV: https://osv.dev/vulnerability/CVE-2024-41952 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-41952/ Summaries are generated and may contain mistakes; the official description above is the record.