Vulnerability in github.com/traefik/traefik/v2 (CVE-2021-32813)
Summary
Vulnerability in github.com/traefik/traefik/v2 (CVE-2021-32813). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.4.13 or later.
Original description
The description as published by the source.
Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.4.13, there exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse. If one has a chain of Traefik middlewares, and one of them sets a request header, then sending a request with a certain Connection header will cause it to be removed before the request is sent. In this case, the backend does not see the request header. A patch is available in version 2.4.13. There are no known workarounds aside from upgrading.
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-2021-32813 has been found in github.com/traefik/traefik/v2.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/traefik/traefik/v2 to 2.4.13 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik/v2 CVE-2021-32813" on the vendor's site.
CVE-2021-32813 (github.com/traefik/traefik/v2) — CWE-913
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.4.13 — apply immediately
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-913) exists in github.com/traefik/traefik/v2.
Check the vendor advisory for the affected versions of github.com/traefik/traefik/v2.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.4.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/traefik/traefik/v2' . 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/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/traefik/traefik/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/traefik/traefik/v2 to 2.4.13ステージング環境で 2.4.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com/traefik/traefik
- patch github.com