Summary
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]
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.
CVE-2024-41952 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122357-a1d24353db4d, 1.80.0-v2.20.0.20240731122357-a1d24353db4d); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2024-41952? CVE-2024-41952 is a medium-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 2.53.0, <= 2.53.8. It is fixed in 2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122357-a1d24353db4d, 1.80.0-v2.20.0.20240731122357-a1d24353db4d.
- How severe is CVE-2024-41952? CVE-2024-41952 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/zitadel/zitadel are affected by CVE-2024-41952? github.com/zitadel/zitadel (go) versions >= 2.53.0, <= 2.53.8 is affected.
- Is there a fix for CVE-2024-41952? Yes. CVE-2024-41952 is fixed in 2.53.9, 2.54.8, 2.55.5, 2.56.2, 2.57.1, 2.58.1, 0.0.0-20240731122357-a1d24353db4d, 1.80.0-v2.20.0.20240731122357-a1d24353db4d. Upgrade to this version or later.
- Is CVE-2024-41952 exploitable, and should I be worried? Whether CVE-2024-41952 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-41952 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-41952?
- Upgrade
github.com/zitadel/zitadelto 2.53.9 or later - Upgrade
github.com/zitadel/zitadelto 2.54.8 or later - Upgrade
github.com/zitadel/zitadelto 2.55.5 or later - Upgrade
github.com/zitadel/zitadelto 2.56.2 or later - Upgrade
github.com/zitadel/zitadelto 2.57.1 or later - Upgrade
github.com/zitadel/zitadelto 2.58.1 or later - Upgrade
github.com/zitadel/zitadelto 0.0.0-20240731122357-a1d24353db4d or later - Upgrade
github.com/zitadel/zitadelto 1.80.0-v2.20.0.20240731122357-a1d24353db4d or later
- Upgrade