CVE-2024-29891

Workarounds

There is no workaround since a patch is already available.

References

None

Questions

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

Credits

Thanks to Amit Laish, GE Vernova for finding and reporting the vulnerability.

ZITADEL users can upload their own avatar image and various image types are allowed.

Due to a missing check, an attacker could upload HTML and pretend it is an image to gain access to the victim's account in certain scenarios.
A possible victim would need to directly open the supposed image in the browser, where a session in ZITADEL needs to be active for this exploit to work.

The exploit could only be reproduced if the victim was using Firefox. Chrome, Safari as well as Edge did not execute the code.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-29891 has a CVSS score of 8.7 (High). 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.42.17, 2.43.11, 2.44.7, 2.45.5, 2.46.5, 2.47.8, 2.48.3); upgrading removes the vulnerable code path.

Kodem intelligence

2.x versions are fixed on >= 2.48.3
2.47.x versions are fixed on >= 2.47.8
2.46.x versions are fixed on >= 2.46.5
2.45.x versions are fixed on >= 2.45.5
2.44.x versions are fixed on >= 2.44.7
2.43.x versions are fixed on >= 2.43.11
2.42.x versions are fixed on >= 2.42.17

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

1. What is CVE-2024-29891? CVE-2024-29891 is a high-severity cross-site scripting (XSS) vulnerability in github.com/zitadel/zitadel (go), affecting versions < 2.42.17. It is fixed in 2.42.17, 2.43.11, 2.44.7, 2.45.5, 2.46.5, 2.47.8, 2.48.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-29891? CVE-2024-29891 has a CVSS score of 8.7 (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-29891? github.com/zitadel/zitadel (go) versions < 2.42.17 is affected.
4. Is there a fix for CVE-2024-29891? Yes. CVE-2024-29891 is fixed in 2.42.17, 2.43.11, 2.44.7, 2.45.5, 2.46.5, 2.47.8, 2.48.3. Upgrade to this version or later.
5. Is CVE-2024-29891 exploitable, and should I be worried? Whether CVE-2024-29891 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-29891 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-29891?
   • Upgrade github.com/zitadel/zitadel to 2.42.17 or later
   • Upgrade github.com/zitadel/zitadel to 2.43.11 or later
   • Upgrade github.com/zitadel/zitadel to 2.44.7 or later
   • Upgrade github.com/zitadel/zitadel to 2.45.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.46.5 or later
   • Upgrade github.com/zitadel/zitadel to 2.47.8 or later
   • Upgrade github.com/zitadel/zitadel to 2.48.3 or later