← Back
CVE-2024-22030
Vulnerability in github.com/rancher/rancher (CVE-2024-22030)
Summary
vulnerability in github.com/rancher/rancher (CVE-2024-22030). Successful exploitation can lead to full system takeover. Exploitable via ``strict``. Mitigation: upgrade to `2.9.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-22030** has been found in github.com/rancher/rancher.
Attackers can target a specific entry point like ``strict`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade github.com/rancher/rancher to **2.9.2** or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2024-22030" on the vendor's site.
CVE-2024-22030 (github.com/rancher/rancher) — CWE-295 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `strict` / `cacerts` / `DownloadWins`
Patched: `2.9.2` — 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
**A vulnerability** (CWE-295) exists in github.com/rancher/rancher. Attackers reach the vulnerable code path via ``strict`` without authentication.
📍 Affected scope
github.com/rancher/rancher — . Attack surface: `strict` / `cacerts` / `DownloadWins`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.9.2**.
🛡️ 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.9.2ステージング環境で 2.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.9.0"},{"fixed":"2.9.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-22030
- package https://github.com/rancher/rancher
- web https://github.com/rancher/rancher/security/advisories/GHSA-h4h5-9833-v2p4
- web https://github.com/rancherlabs/support-tools/tree/master/windows-agent-strict-verify
- web https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/tls-settings
- web https://bugzilla.suse.com/show_bug.cgi?id=CVE-2024-22030
- web https://pkg.go.dev/vuln/GO-2024-3161