← Back
CVE-2024-22031
Authorization Flaw in github.com/rancher/rancher (CVE-2024-22031)
Summary
vulnerability in github.com/rancher/rancher (CVE-2024-22031). Successful exploitation can lead to full system takeover.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-22031** has been found in github.com/rancher/rancher.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2024-22031" on the vendor's site.
CVE-2024-22031 (github.com/rancher/rancher) — CWE-863 /
Attack vector: remote (network-reachable) / no user interaction
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
**incorrect authorization** (CWE-863) exists in github.com/rancher/rancher.
📍 Affected scope
github.com/rancher/rancher — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 し、稼働しているサービス・バージョンを把握する。
-
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":"0"}]}]
References
- advisory https://github.com/rancher/rancher/security/advisories/GHSA-8h6m-wv39-239m
- package https://github.com/rancher/rancher
- web https://github.com/rancher/rancher/commit/7f16b596120dd382ce6e9ed0baf83bc23f633054
- web https://github.com/rancher/rancher/commit/9c1d1c2bfcba36ae4f06c1fd043eb539ad801d4d
- web https://github.com/rancher/rancher/commit/b0be28f86fc556414bd9b323f05b2b4bf8317c2d
- web https://github.com/rancher/rancher/commit/f036e8b6ab726c3abbc03bbf7c8d0d53373c84e5
- web https://pkg.go.dev/vuln/GO-2025-3647