Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-31247

Vulnerability in github.com/rancher/rancher (CVE-2022-31247)

Summary

Vulnerability in github.com/rancher/rancher (CVE-2022-31247). Successful exploitation can lead to full system takeover. Exploitable via owner. Mitigation: upgrade to 2.6.7 or later.

Original description

The description as published by the source.

Impact

An issue was discovered in Rancher versions up to and including 2.5.15 and 2.6.6 where a flaw with authorization logic allows privilege escalation through cluster role template binding (CRTB) and project role template binding (PRTB). This issue does not affect the local cluster, it affects only downstream clusters.

The vulnerability can be exploited by any user who has permissions to create/edit cluster role template bindings or project role template bindings (such as cluster-owner, manage cluster members, project-owner and manage project members) to gain owner permission in another project in the same cluster or in another project on a different downstream cluster.

  • The user must have kubectl access in the local cluster to exploit this scenario.

  • This can only be abused to gain cluster-owner permission on a different downstream cluster if the user is already cluster-owner on at least one downstream cluster.

  • Example of a modified CRTB (note: the clusterName points to the cluster ID of the cluster that the privileges will be escalated and namespace points to the current cluster ID that the user has permissions):

kubectl edit clusterroletemplatebindings crtb- -n c-
---
apiVersion: management.cattle.io/v3
clusterName: 
kind: ClusterRoleTemplateBinding
metadata:
  annotations:
     
  finalizers:
  -  
  generateName: crtb-
  labels:
     
    cattle.io/creator: norman
  name: crtb-
  namespace: c-
roleTemplateName: cluster-own…

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-2022-31247 has been found in github.com/rancher/rancher.
Attackers can target a specific entry point like owner 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.6.7 or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2022-31247" on the vendor's site.

CVE-2022-31247 (github.com/rancher/rancher) — CWE-285
Attack vector: remote (network-reachable) / no user interaction
Attack surface: owner / kubectl / clusterName / namespace
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.

❓ What is the problem

A vulnerability (CWE-285) exists in github.com/rancher/rancher. Attackers reach the vulnerable code path via owner.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rancher/rancher. Attack surface: owner / kubectl / clusterName / namespace.

🔥 Severity

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

🔧 How to fix

Update to 2.6.7.

🛡️ 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

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 patch patch 
    Upgrade github.com/rancher/rancher to 2.6.7

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

  3. 3
    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.6.0"},{"fixed":"2.6.7"}]}]

References

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