# CVE-2024-28869: Possible denial of service vulnerability with Content-length header in Traefik

> Attackers can cause indefinite hangs in Traefik by sending GET requests with a Content-length header, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** ECHO-f160-1deb-c3b0, GHSA-4vwx-54mw-vqfw, GO-2024-2722

## What is CVE-2024-28869?

CVE-2024-28869 is a high-severity denial of service vulnerability in Traefik Traefik, published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traefik is an HTTP reverse proxy and load balancer. In affected versions sending a GET request to any Traefik endpoint with the "Content-length" request header results in an indefinite hang with the default configuration. This vulnerability can be exploited by attackers to induce a denial of service. This vulnerability has been addressed in version 2.11.2 and 3.0.0-rc5. Users are advised to upgrade. For affected versions, this vulnerability can be mitigated by configuring the readTimeout option.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2024-28869?

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.2 |
| `github.com/traefik/traefik` | Go | All versions | 2.11.2 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.2 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.2 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.2 |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.0.0-rc5 |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.0.0-rc5 |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0-beta3 | 3.0.0-rc5 |

Products: Traefik Traefik.

## How do I fix CVE-2024-28869?

Upgrade github.com/traefik/traefik to 2.11.2 or later.

## Is CVE-2024-28869 being exploited?

There is no known exploitation of CVE-2024-28869 in the wild and no public exploit code.

## Other vulnerabilities in Traefik Traefik

- [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28869 and fix it if it is affected.

What it is: CVE-2024-28869 is a high-severity denial of service vulnerability in Traefik Traefik, published on 12 Apr 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-28869 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.2
- github.com/traefik/traefik (Go): affected all versions; fixed in 2.11.2
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.2
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.2
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.2
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.0.0-rc5
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.0.0-rc5
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0-beta3; fixed in 3.0.0-rc5

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-28869/ (Markdown: https://insights.sbomify.com/CVE-2024-28869/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28869
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28869
- OSV: https://osv.dev/vulnerability/CVE-2024-28869

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-28869/
Summaries are generated and may contain mistakes; the official description above is the record.
