Open Redirect in github.com/traefik/traefik (CVE-2020-15129)
Summary
Vulnerability in github.com/traefik/traefik (CVE-2020-15129). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.26 or later.
Original description
The description as published by the source.
In Traefik before versions 1.7.26, 2.2.8, and 2.3.0-rc3, there exists a potential open redirect vulnerability in Traefik's handling of the "X-Forwarded-Prefix" header. The Traefik API dashboard component doesn't validate that the value of the header "X-Forwarded-Prefix" is a site relative path and will redirect to any header provided URI. Successful exploitation of an open redirect can be used to entice victims to disclose sensitive information. Active Exploitation of this issue is unlikely as it would require active header injection, however the Traefik team addressed this issue nonetheless to prevent abuse in e.g. cache poisoning scenarios.
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-2020-15129 has been found in github.com/traefik/traefik.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/traefik/traefik to 1.7.26 or later.
If unsure, ask your IT team or search "github.com/traefik/traefik CVE-2020-15129" on the vendor's site.
CVE-2020-15129 (github.com/traefik/traefik) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.7.26 — 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-601) exists in github.com/traefik/traefik.
Check the vendor advisory for the affected versions of github.com/traefik/traefik.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.26.
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' . 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 patch patch
Upgrade github.com/traefik/traefik to 1.7.26ステージング環境で 1.7.26 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com