CVE-2024-39683

Workarounds

There is no workaround since a patch is already available.

References

• https://github.com/zitadel/zitadel/pull/8231
• https://discord.com/channels/927474939156643850/1254096852937347153
• https://github.com/zitadel/zitadel/issues/8213

Questions

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

Credits

Thanks to @cybertransformer, @Avolicious, @AmirhoseinBrz and @srividyaj for finding and reporting the vulnerability.

ZITADEL provides users the ability to list all user sessions of the current user agent (browser) by API and in the Console UI.

Due to a missing check, user sessions without that information (e.g. when created though the session service) were incorrectly listed exposing potentially other user's sessions.

Note that the Login UI was never affected and there was no possibility to take over such a session.

CVE-2024-39683 has a CVSS score of 5.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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.8, 2.54.5, 2.55.1); upgrading removes the vulnerable code path.

Kodem intelligence

2.x versions are fixed on >= 2.55.1
2.54.x versions are fixed on >= 2.54.5
2.53.x versions are fixed on >= 2.53.8

ZITADEL recommends upgrading to the latest versions available in due course.

1. What is CVE-2024-39683? CVE-2024-39683 is a medium-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 2.0.0, <= 2.53.7. It is fixed in 2.53.8, 2.54.5, 2.55.1.
2. How severe is CVE-2024-39683? CVE-2024-39683 has a CVSS score of 5.7 (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.
3. Which versions of github.com/zitadel/zitadel are affected by CVE-2024-39683? github.com/zitadel/zitadel (go) versions >= 2.0.0, <= 2.53.7 is affected.
4. Is there a fix for CVE-2024-39683? Yes. CVE-2024-39683 is fixed in 2.53.8, 2.54.5, 2.55.1. Upgrade to this version or later.
5. Is CVE-2024-39683 exploitable, and should I be worried? Whether CVE-2024-39683 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-39683 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-39683?
   • Upgrade github.com/zitadel/zitadel to 2.53.8 or later
   • Upgrade github.com/zitadel/zitadel to 2.54.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.55.1 or later