# CVE-2024-45410: HTTP client can remove the X-Forwarded headers in Traefik - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 19 Sep 2024 - **Updated:** 20 Sep 2024 - **Also known as:** ECHO-678c-79a3-e71d, GHSA-62c8-mh53-4cqv, GO-2024-3135, openSUSE-SU-2024:14365-1, openSUSE-SU-2024:14367-1 ## What is CVE-2024-45410? CVE-2024-45410 is a critical vulnerability in Traefik Traefik, published on 19 Sep 2024. ### Official description Traefik is a golang, Cloud Native Application Proxy. When a HTTP request is processed by Traefik, certain HTTP headers such as X-Forwarded-Host or X-Forwarded-Port are added by Traefik before the request is routed to the application. For a HTTP client, it should not be possible to remove or modify these headers. Since the application trusts the value of these headers, security implications might arise, if they can be modified. For HTTP/1.1, however, it was found that some of theses custom headers can indeed be removed and in certain cases manipulated. The attack relies on the HTTP/1.1 behavior, that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been addressed in release versions 2.11.9 and 3.1.3. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-348 (Use of Less Trusted Source), CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2024-45410? 9 open source packages ship an affected version, including github.com/traefik/traefik, github.com/traefik/traefik/v2 and github.com/traefik/traefik/v3. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik` | Go | All versions | 2.11.9 | | `github.com/traefik/traefik` | Go | All versions | 2.11.9 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.9 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.9 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.9 | | `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.1.3 | | `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.1.3 | | `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.1.3 | | `traefik` | openSUSE:Tumbleweed | All versions | 3.1.4-1.1 | | `traefik2` | openSUSE:Tumbleweed | All versions | 2.11.10-1.1 | Products: Traefik Traefik. ## How do I fix CVE-2024-45410? Upgrade github.com/traefik/traefik to 2.11.9 or later. ## Is CVE-2024-45410 being exploited? There is no known exploitation of CVE-2024-45410 in the wild and no public exploit code. Public exploit code: - A proof of concept of traefik CVE to understand the impact (github_poc): https://github.com/jphetphoumy/traefik-CVE-2024-45410-poc ## Other vulnerabilities in Traefik Traefik - [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3) - [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3) - [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1) - [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8) - [CVE-2025-32431](https://insights.sbomify.com/CVE-2025-32431/): Traefik has a possible vulnerability with the path matchers (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-45410 and fix it if it is affected. What it is: CVE-2024-45410 is a critical vulnerability in Traefik Traefik, published on 19 Sep 2024. Exploitation: There is no known exploitation of CVE-2024-45410 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/traefik/traefik (Go): affected all versions; no fix listed - github.com/traefik/traefik (Go): affected all versions; fixed in 2.11.9 - github.com/traefik/traefik (Go): affected all versions; fixed in 2.11.9 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.9 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.9 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.9 - github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.1.3 - github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.1.3 - github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.1.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-45410/ (Markdown: https://insights.sbomify.com/CVE-2024-45410/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45410 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45410 - OSV: https://osv.dev/vulnerability/CVE-2024-45410 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-45410/ Summaries are generated and may contain mistakes; the official description above is the record.