CVE-2024-49757

Workarounds

Updating to the patched version is the recommended solution.

Questions

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

Credits

Thanks to @sevensolutions and @evilgensec for disclosing this!

Zitadel allows administrators to disable the user self-registration. Due to a missing security check in versions prior to 2.63.4, disabling the "User Registration allowed" option only hid the registration button on the login page. Users could bypass this restriction by directly accessing the registration URL (/ui/login/loginname) and register a user that way.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2024-49757 has a CVSS score of 7.5 (High). 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.63.5, 2.62.7, 2.61.4, 2.60.4, 2.59.5, 2.58.7); upgrading removes the vulnerable code path.

Kodem intelligence

2.x versions are fixed on >= 2.64.0
2.63.x versions are fixed on >= 2.63.5
2.62.x versions are fixed on >= 2.62.7
2.61.x versions are fixed on >= 2.61.4
2.60.x versions are fixed on >= 2.60.4
2.59.x versions are fixed on >= 2.59.5
2.58.x versions are fixed on >= 2.58.7

1. What is CVE-2024-49757? CVE-2024-49757 is a high-severity improper authentication vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 2.63.0, < 2.63.5. It is fixed in 2.63.5, 2.62.7, 2.61.4, 2.60.4, 2.59.5, 2.58.7. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2024-49757? CVE-2024-49757 has a CVSS score of 7.5 (High). 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.
3. Which versions of github.com/zitadel/zitadel are affected by CVE-2024-49757? github.com/zitadel/zitadel (go) versions >= 2.63.0, < 2.63.5 is affected.
4. Is there a fix for CVE-2024-49757? Yes. CVE-2024-49757 is fixed in 2.63.5, 2.62.7, 2.61.4, 2.60.4, 2.59.5, 2.58.7. Upgrade to this version or later.
5. Is CVE-2024-49757 exploitable, and should I be worried? Whether CVE-2024-49757 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
6. What actually determines whether CVE-2024-49757 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.
7. How do I fix CVE-2024-49757?
   • Upgrade github.com/zitadel/zitadel to 2.63.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.62.7 or later
   • Upgrade github.com/zitadel/zitadel to 2.61.4 or later
   • Upgrade github.com/zitadel/zitadel to 2.60.4 or later
   • Upgrade github.com/zitadel/zitadel to 2.59.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.58.7 or later