CVE-2024-29892

Workarounds

No workaround available since a patch is available

Credits

Many thanks to @schettn whose disclosure of another topic lead us to find this issue.

Under certain circumstances an action could set reserved claims managed by ZITADEL.

For example it would be possible to set the claim urn:zitadel:iam:user:resourceowner:name

{"urn:zitadel:iam:user:resourceowner:name": "ACME"}

if it was not set by ZITADEL itself.

To compensate for this we introduced a protection that does prevent actions from changing claims that start with urn:zitadel:iam

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2024-29892 has a CVSS score of 6.1 (High). The vector is network-reachable, high 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

1. What is CVE-2024-29892? CVE-2024-29892 is a high-severity incorrect authorization 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. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2024-29892? CVE-2024-29892 has a CVSS score of 6.1 (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-29892? github.com/zitadel/zitadel (go) versions < 2.42.17 is affected.
4. Is there a fix for CVE-2024-29892? Yes. CVE-2024-29892 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-29892 exploitable, and should I be worried? Whether CVE-2024-29892 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-29892 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-29892?
   • 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