# CVE-2024-32967: Zitadel exposes internal database user name and host information > Attackers can obtain internal database connection details when database connectivity fails, exposing sensitive infrastructure information. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 May 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-q5qj-x2h5-3945, GO-2024-2804 ## What is CVE-2024-32967? CVE-2024-32967 is a medium-severity vulnerability in zitadel, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Zitadel is an open source identity management system. In case ZITADEL could not connect to the database, connection information including db name, username and db host name could be returned to the user. This has been addressed in all supported release branches in a point release. There is no workaround since a patch is already available. Users are advised to upgrade. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2024-32967? 11 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.45.7 | | `github.com/zitadel/zitadel` | Go | All versions | 2.45.7 | | `github.com/zitadel/zitadel` | Go | From 2.47.0 | 2.47.10 | | `github.com/zitadel/zitadel` | Go | From 2.47.0 | 2.47.10 | | `github.com/zitadel/zitadel` | Go | From 2.48.0 | 2.48.5 | | `github.com/zitadel/zitadel` | Go | From 2.48.0 | 2.48.5 | | `github.com/zitadel/zitadel` | Go | From 2.49.0 | 2.49.5 | | `github.com/zitadel/zitadel` | Go | From 2.49.0 | 2.49.5 | | `github.com/zitadel/zitadel` | Go | From 2.50.0 | 2.50.3 | | `github.com/zitadel/zitadel` | Go | From 2.50.0 | 2.50.3 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-32967? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 2.45.7, 2.47.10, 2.48.5 or 2.49.5. ## Is CVE-2024-32967 being exploited? There is no known exploitation of CVE-2024-32967 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-32967 and fix it if it is affected. What it is: CVE-2024-32967 is a medium-severity vulnerability in zitadel, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-32967 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.45.7 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.45.7 - github.com/zitadel/zitadel (Go): affected from 2.47.0; fixed in 2.47.10 - github.com/zitadel/zitadel (Go): affected from 2.47.0; fixed in 2.47.10 - github.com/zitadel/zitadel (Go): affected from 2.48.0; fixed in 2.48.5 - github.com/zitadel/zitadel (Go): affected from 2.48.0; fixed in 2.48.5 - github.com/zitadel/zitadel (Go): affected from 2.49.0; fixed in 2.49.5 - github.com/zitadel/zitadel (Go): affected from 2.49.0; fixed in 2.49.5 - github.com/zitadel/zitadel (Go): affected from 2.50.0; fixed in 2.50.3 - github.com/zitadel/zitadel (Go): affected from 2.50.0; fixed in 2.50.3 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-32967/ (Markdown: https://insights.sbomify.com/CVE-2024-32967/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32967 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32967 - OSV: https://osv.dev/vulnerability/CVE-2024-32967 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32967/ Summaries are generated and may contain mistakes; the official description above is the record.