Vulnerability in github.com/traefik/traefik (CVE-2024-28869)
Summary
Vulnerability in github.com/traefik/traefik (CVE-2024-28869). Risk of unauthorized operations or information disclosure. Exploitable via body. Mitigation: upgrade to 2.11.2 or later.
Original description
The description as published by the source.
There is a potential vulnerability in Traefik managing requests with Content-length and no body .
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.
Patches
- https://github.com/traefik/traefik/releases/tag/v2.11.2
- https://github.com/traefik/traefik/releases/tag/v3.0.0-rc5
Workarounds
For affected versions, this vulnerability can be mitigated by configuring the readTimeout option.
For more information
If you have any questions or comments about this advisory, please open an issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-28869 has been found in github.com/traefik/traefik.
Attackers can target a specific entry point like body over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/traefik/traefik to 2.11.2 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik CVE-2024-28869" on the vendor's site.
CVE-2024-28869 (github.com/traefik/traefik) — CWE-404
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: body / GET
Patched: 2.11.2 — apply immediately
Workaround: For affected versions, this vulnerability can be mitigated by configuring the readTimeout option.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-404) exists in github.com/traefik/traefik. Attackers reach the vulnerable code path via body without authentication.
Check the vendor advisory for the affected versions of github.com/traefik/traefik. Attack surface: body / GET.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.11.2.
Workaround: For affected versions, this vulnerability can be mitigated by configuring the readTimeout option.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/traefik/traefik' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/traefik/traefik' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/traefik/traefikを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
For affected versions, this vulnerability can be mitigated by configuring the [readTimeout](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) option.パッチが適用されるまでの応急処置として、For affected versions, this vulnerability can be mitigated by configuring the readTimeout option. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/traefik/traefik to 2.11.2ステージング環境で 2.11.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web doc.traefik.io
- web github.com
- web github.com