Vulnerability in github.com/rancher/rancher (CVE-2021-36782)
Summary
Vulnerability in github.com/rancher/rancher (CVE-2021-36782). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.6.7 or later.
Original description
The description as published by the source.
A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners, Project Members and User Base to use the Kubernetes API to retrieve plaintext version of sensitive data. This issue affects: SUSE Rancher Rancher versions prior to 2.5.16; Rancher versions prior to 2.6.7.
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-36782 has been found in github.com/rancher/rancher.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/rancher/rancher to 2.6.7 or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2021-36782" on the vendor's site.
CVE-2021-36782 (github.com/rancher/rancher) — CWE-312
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.6.7 — 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-312) exists in github.com/rancher/rancher.
Check the vendor advisory for the affected versions of github.com/rancher/rancher.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.6.7.
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/rancher/rancher' . 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/rancher/rancher' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/rancher/rancherを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/rancher/rancher to 2.6.7ステージング環境で 2.6.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- report github.com
- report bugzilla.suse.com