Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-22647

Vulnerability in github.com/rancher/rancher (CVE-2023-22647)

Summary

Vulnerability in github.com/rancher/rancher (CVE-2023-22647). Successful exploitation can lead to full system takeover. Exploitable via local. Mitigation: upgrade to 2.7.4 or later.

Original description

The description as published by the source.

Impact

A vulnerability has been identified which enables Standard users or above to elevate their permissions to Administrator in the local cluster.

The local cluster means the cluster where Rancher is installed. It is named local inside the list of clusters in the Rancher UI.

Standard users could leverage their existing permissions to manipulate Kubernetes secrets in the local cluster, resulting in the secret being deleted, but their read-level permissions to the secret being preserved. When this operation was followed-up by other specially crafted commands, it could result in the user gaining access to tokens belonging to service accounts in the local cluster.

Users that have custom global roles which grant create and delete permissions on secrets would also be able to exploit this vulnerability.

Users with audit logs enabled in Rancher can try to identify possible abuses of this issue by going through the logs. To sieve through the data filter by kind: Secret with type: provisioning.cattle.io/cloud-credential, then investigate all log entries that affect that specific resource. A secondary check would be to filter by all operations with Opaque…

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-2023-22647 has been found in github.com/rancher/rancher.
Attackers can target a specific entry point like local over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/rancher/rancher to 2.7.4 or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2023-22647" on the vendor's site.

CVE-2023-22647 (github.com/rancher/rancher) — CWE-267
Attack vector: remote (network-reachable) / no user interaction
Attack surface: local / create / delete / secrets
Patched: 2.7.4 — apply immediately
Workaround: There is no direct mitigation besides updating Rancher to a patched version.
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-267) exists in github.com/rancher/rancher. Attackers reach the vulnerable code path via local.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rancher/rancher. Attack surface: local / create / delete / secrets.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.7.4.

🛡️ Workaround

Workaround: There is no direct mitigation besides updating Rancher to a patched version.

🔍 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There is no direct mitigation besides updating Rancher to a patched version.

    パッチが適用されるまでの応急処置として、There is no direct mitigation besides updating Rancher to a patched version. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/rancher/rancher to 2.7.4

    ステージング環境で 2.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/rancher/rancher
[{"type":"SEMVER","events":[{"introduced":"2.7.0"},{"fixed":"2.7.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details