← Back
CVE-2019-13209
Cross-Site Request Forgery (CSRF) in github.com/rancher/rancher (CVE-2019-13209)
Summary
vulnerability in github.com/rancher/rancher (CVE-2019-13209). Confidential information can be exposed externally. Mitigation: upgrade to `2.2.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2019-13209** has been found in github.com/rancher/rancher.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade github.com/rancher/rancher to **2.2.5** or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2019-13209" on the vendor's site.
CVE-2019-13209 (github.com/rancher/rancher) — CWE-352 /
Attack vector: remote (network-reachable)
Patched: `2.2.5` — 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.
❓ What is the problem
**CSRF** (CWE-352) exists in github.com/rancher/rancher.
📍 Affected scope
github.com/rancher/rancher — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.2.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/rancher/rancher' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/rancher/rancher' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/rancher/rancher` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/rancher/rancher to 2.2.5ステージング環境で 2.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/rancher/rancher
[{"type":"SEMVER","events":[{"introduced":"2.2.0"},{"fixed":"2.2.5"}]}]
References
- advisory https://github.com/advisories/GHSA-xhg2-rvm8-w2jh
- advisory https://nvd.nist.gov/vuln/detail/CVE-2019-13209
- package https://github.com/rancher/rancher
- web https://github.com/rancher/rancher/commit/0ddffe484adccb9e37d9432e8e625d8ebbfb0088
- web https://forums.rancher.com/t/rancher-release-v2-2-5-addresses-rancher-cve-2019-13209/14801