# CVE-2024-29892: ZITADEL's actions can overload reserved claims > Attackers can manipulate reserved claims via actions to escalate privileges or bypass security controls in ZITADEL authentication flows. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 27 Mar 2024 - **Updated:** 13 Aug 2024 - **Also known as:** GHSA-gp8g-f42f-95q2, GO-2024-2664 ## What is CVE-2024-29892? CVE-2024-29892 is a medium-severity vulnerability in zitadel, published on 27 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description ZITADEL, open source authentication management software, uses Go templates to render the login UI. 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`. To compensate for this we introduced a protection that does prevent actions from changing claims that start with `urn:zitadel:iam`. This vulnerability is fixed in 2.48.3, 2.47.8, 2.46.5, 2.45.5, 2.44.7, 2.43.11, and 2.42.17. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2024-29892? 15 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel` | Go | All versions | None | | `github.com/zitadel/zitadel` | Go | All versions | 2.42.17 | | `github.com/zitadel/zitadel` | Go | All versions | 2.42.17 | | `github.com/zitadel/zitadel` | Go | From 2.43.0 | 2.43.11 | | `github.com/zitadel/zitadel` | Go | From 2.43.0 | 2.43.11 | | `github.com/zitadel/zitadel` | Go | From 2.44.0 | 2.44.7 | | `github.com/zitadel/zitadel` | Go | From 2.44.0 | 2.44.7 | | `github.com/zitadel/zitadel` | Go | From 2.45.0 | 2.45.5 | | `github.com/zitadel/zitadel` | Go | From 2.45.0 | 2.45.5 | | `github.com/zitadel/zitadel` | Go | From 2.46.0 | 2.46.5 | | `github.com/zitadel/zitadel` | Go | From 2.46.0 | 2.46.5 | | `github.com/zitadel/zitadel` | Go | From 2.47.0 | 2.47.8 | | `github.com/zitadel/zitadel` | Go | From 2.47.0 | 2.47.8 | | `github.com/zitadel/zitadel` | Go | From 2.48.0 | 2.48.3 | | `github.com/zitadel/zitadel` | Go | From 2.48.0 | 2.48.3 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-29892? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 2.42.17, 2.43.11, 2.44.7 or 2.45.5. ## Is CVE-2024-29892 being exploited? There is no known exploitation of CVE-2024-29892 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-29892 and fix it if it is affected. What it is: CVE-2024-29892 is a medium-severity vulnerability in zitadel, published on 27 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-29892 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel (Go): affected all versions; no fix listed - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.42.17 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.42.17 - github.com/zitadel/zitadel (Go): affected from 2.43.0; fixed in 2.43.11 - github.com/zitadel/zitadel (Go): affected from 2.43.0; fixed in 2.43.11 - github.com/zitadel/zitadel (Go): affected from 2.44.0; fixed in 2.44.7 - github.com/zitadel/zitadel (Go): affected from 2.44.0; fixed in 2.44.7 - github.com/zitadel/zitadel (Go): affected from 2.45.0; fixed in 2.45.5 - github.com/zitadel/zitadel (Go): affected from 2.45.0; fixed in 2.45.5 - github.com/zitadel/zitadel (Go): affected from 2.46.0; fixed in 2.46.5 - github.com/zitadel/zitadel (Go): affected from 2.46.0; fixed in 2.46.5 - github.com/zitadel/zitadel (Go): affected from 2.47.0; fixed in 2.47.8 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-29892/ (Markdown: https://insights.sbomify.com/CVE-2024-29892/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29892 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29892 - OSV: https://osv.dev/vulnerability/CVE-2024-29892 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-29892/ Summaries are generated and may contain mistakes; the official description above is the record.