# CVE-2024-49753: Denied Host Validation Bypass in Zitadel Actions > Attackers can bypass localhost restrictions in Zitadel actions via DNS tricks to access internal endpoints, requiring a patch. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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:** Not needed - **Fix available:** Yes - **Published:** 25 Oct 2024 - **Updated:** 25 Oct 2024 - **Also known as:** GHSA-6cf5-w9h3-4rqv, GO-2024-3216 ## What is CVE-2024-49753? CVE-2024-49753 is a medium-severity server-side request forgery vulnerability in zitadel, published on 25 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Zitadel is open-source identity infrastructure software. Versions prior to 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 have a flaw in the URL validation mechanism of Zitadel actions allows bypassing restrictions intended to block requests to localhost (127.0.0.1). The isHostBlocked check, designed to prevent such requests, can be circumvented by creating a DNS record that resolves to 127.0.0.1. This enables actions to send requests to localhost despite the intended security measures. This vulnerability potentially allows unauthorized access to unsecured internal endpoints, which may contain sensitive information or functionalities. Versions 2.64.1, 2.63.6, 2.62.8, 2.61.4, 2.60.4, 2.59.5, and 2.58.7 contain a patch. No known workarounds are available. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2024-49753? 19 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 | 0.0.0-20241022141644-79fb4cc1cc6e | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20241022141644-79fb4cc1cc6e | | `github.com/zitadel/zitadel` | Go | From 0.0.0 | 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e | | `github.com/zitadel/zitadel` | Go | From 0.0.0 | 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e | | `github.com/zitadel/zitadel` | Go | From 1.80.1 | 2.58.7 | | `github.com/zitadel/zitadel` | Go | From 1.80.1 | 2.58.7 | | `github.com/zitadel/zitadel` | Go | From 2.59.0 | 2.59.5 | | `github.com/zitadel/zitadel` | Go | From 2.59.0 | 2.59.5 | | `github.com/zitadel/zitadel` | Go | From 2.60.0 | 2.60.4 | | `github.com/zitadel/zitadel` | Go | From 2.60.0 | 2.60.4 | | `github.com/zitadel/zitadel` | Go | From 2.61.0 | 2.61.4 | | `github.com/zitadel/zitadel` | Go | From 2.61.0 | 2.61.4 | | `github.com/zitadel/zitadel` | Go | From 2.62.0 | 2.62.8 | | `github.com/zitadel/zitadel` | Go | From 2.62.0 | 2.62.8 | | `github.com/zitadel/zitadel` | Go | From 2.63.0 | 2.63.6 | | `github.com/zitadel/zitadel` | Go | From 2.63.0 | 2.63.6 | | `github.com/zitadel/zitadel` | Go | From 2.64.0 | 2.64.1 | | `github.com/zitadel/zitadel` | Go | From 2.64.0 | 2.64.1 | Products: Zitadel Zitadel. ## How do I fix CVE-2024-49753? Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 0.0.0-20241022141644-79fb4cc1cc6e, 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e, 2.58.7 or 2.59.5. ## Is CVE-2024-49753 being exploited? There is no known exploitation of CVE-2024-49753 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-49753 and fix it if it is affected. What it is: CVE-2024-49753 is a medium-severity server-side request forgery vulnerability in zitadel, published on 25 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-49753 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 0.0.0-20241022141644-79fb4cc1cc6e - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20241022141644-79fb4cc1cc6e - github.com/zitadel/zitadel (Go): affected from 0.0.0; fixed in 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e - github.com/zitadel/zitadel (Go): affected from 0.0.0; fixed in 1.80.0-v2.20.0.20241022141644-79fb4cc1cc6e - github.com/zitadel/zitadel (Go): affected from 1.80.1; fixed in 2.58.7 - github.com/zitadel/zitadel (Go): affected from 1.80.1; fixed in 2.58.7 - github.com/zitadel/zitadel (Go): affected from 2.59.0; fixed in 2.59.5 - github.com/zitadel/zitadel (Go): affected from 2.59.0; fixed in 2.59.5 - github.com/zitadel/zitadel (Go): affected from 2.60.0; fixed in 2.60.4 - github.com/zitadel/zitadel (Go): affected from 2.60.0; fixed in 2.60.4 - github.com/zitadel/zitadel (Go): affected from 2.61.0; fixed in 2.61.4 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-49753/ (Markdown: https://insights.sbomify.com/CVE-2024-49753/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49753 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49753 - OSV: https://osv.dev/vulnerability/CVE-2024-49753 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-49753/ Summaries are generated and may contain mistakes; the official description above is the record.