CVE-2022-31247: Github.com/rancher/rancher Rancher Has Downstream Cluster Privilege Vulnerability

CRITICAL
Advisory Identifier: GHSA-6x34-89p7-95wg
CVSS 9.1
CWE-285 CWE-863
Published
Advisory Summary

CVE-2022-31247 is a CRITICAL (CVSS 9.1) rancher has downstream cluster privilege vulnerability (CWE-285: Improper Authorization) affecting Github.com/rancher/rancher libraries in the Go ecosystem. The issue involves rancher has downstream cluster privilege escalation through cluster and project role template binding (crtb/prtb). Remediation is available by upgrading affected packages to version 2.5.16, 2.6.7.

CVE-2022-31247 at a Glance

CVE Identifier CVE-2022-31247
GHSA Identifier GHSA-6x34-89p7-95wg
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-285: Improper Authorization
Affected Product Github.com/rancher/rancher
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2022-31247

To remediate this vulnerability, upgrade all affected Github.com/rancher/rancher dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rancher/rancher fixed: 2.5.16
Upgrade github.com/rancher/rancher to 2.5.16
github.com/rancher/rancher fixed: 2.6.7
Upgrade github.com/rancher/rancher to 2.6.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rancher/rancher

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-31247, inspect your project dependencies for Github.com/rancher/rancher:

inspect dependencies for github.com/rancher/rancher

Analyze the terminal output to locate any version of Github.com/rancher/rancher in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.16), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Github.com/rancher/rancher, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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-<crtb-ID> -n c-<cluster-ID> --- apiVersion: management.cattle.io/v3 clusterName: <ID-of-the-cluster-to-escalate> kind: ClusterRoleTemplateBinding metadata: annotations: <omitted> finalizers: - <omitted> generateName: crtb- labels: <omitted> cattle.io/creator: norman name: crtb-<crtb-ID> namespace: c-<current-cluster-ID> roleTemplateName: cluster-owner userName: u-<user-ID> userPrincipalName: local://u-<user-ID> ``` An artifact to flag the exploitation of this issue is that the `namespace` of the CRTB/PRTB will not match the cluster name (`clusterName`) of the CRTB/PRTB. For example, every CRTB in the `c-123xyz` namespace should have a cluster name of `c-123xyz`. If instead, the cluster name is `c-abc567`, for example, this is likely a result of a user exploiting this flaw. For more information about cluster and project roles, please consult Rancher's [documentation](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/). ### Patches Patched versions include releases 2.5.16, 2.6.7 and later versions. ### Workarounds Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions. **Important:** - It is highly advised to check the local and downstream clusters for potential unrecognized CRTBs (`kubectl get clusterroletemplatebindings -A`) and PRTBs (`kubectl get projectroletemplatebindings -A`) assignments. - The ability to add other users to projects and clusters is a highly-privileged permission which may result in users being able to operate beyond their explicitly specified RBAC. It is recommended that this permission be granted selectively. The following script can be used as a helper to detect possible deviations of CRTBs and PRTBs that do not match the expected value. Further investigation is required to determine if the flagged objects were maliciously modified or not. The script requires `kubectl` access to the `local` cluster and the `jq` command. ```shell #!/usr/bin/env bash echo "CRTBs that don't match cluster:" kubectl get clusterroletemplatebindings -A -o=jsonpath="{range .items[?(@.clusterName!=@.metadata.namespace)]}{.metadata.name}{'\n'}{end}" echo "PRTBs that don't match project:" kubectl get projectroletemplatebindings -A -ojson | jq -r '.items[]|.metadata as $m|select(.projectName|endswith($m.namespace)|not)|.metadata.name' ``` ### For more information If you have any questions or comments about this advisory: * Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. * Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. * Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

CVE-2022-31247 Affected Github.com/rancher/rancher Versions

2 component(s)
Fixed Versions:
2.5.162.6.7
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rancher/rancher
Go
≥ 2.5.0
< 2.5.16
2.5.16
github.com/rancher/rancher
Go
≥ 2.6.0
< 2.6.7
2.6.7

References

Frequently Asked Questions

What is CVE-2022-31247?
CVE-2022-31247 is a security vulnerability in Github.com/rancher/rancher involving Rancher has downstream cluster privilege escalation through cluster and project role template binding (CRTB/PRTB) under CWE-285: Improper Authorization.
Which Github.com/rancher/rancher versions are affected?
Affected versions include releases prior to 2.5.16, 2.6.7 across affected packages: github.com/rancher/rancher.
What version fixes CVE-2022-31247?
Upgrading to 2.5.16, 2.6.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/rancher affected?
Yes, github.com/rancher/rancher is affected in releases prior to 2.5.16, 2.6.7. Upgrade your dependency to 2.5.16, 2.6.7 or later.
What is the CVSS score of CVE-2022-31247?
CVE-2022-31247 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2022-31247?
CVE-2022-31247 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2022-31247?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/rancher'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6x34-89p7-95wg",
  "modified" : "2026-03-03T14:50:12Z",
  "published" : "2026-03-03T14:50:12Z",
  "aliases" : [ "CVE-2022-31247" ],
  "summary" : "Rancher has downstream cluster privilege escalation through cluster and project role template binding (CRTB/PRTB)",
  "details" : "### Impact\n\nAn 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.\n\nThe 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.\n\n   - The user must have `kubectl` access in the local cluster to exploit this scenario.\n\n   - 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.\n\n   - 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):\n```\nkubectl edit clusterroletemplatebindings crtb-<crtb-ID> -n c-<cluster-ID>\n---\napiVersion: management.cattle.io/v3\nclusterName: <ID-of-the-cluster-to-escalate>\nkind: ClusterRoleTemplateBinding\nmetadata:\n  annotations:\n    <omitted> \n  finalizers:\n  - <omitted> \n  generateName: crtb-\n  labels:\n    <omitted> \n    cattle.io/creator: norman\n  name: crtb-<crtb-ID>\n  namespace: c-<current-cluster-ID>\nroleTemplateName: cluster-owner\nuserName: u-<user-ID>\nuserPrincipalName: local://u-<user-ID>\n```\n\nAn artifact to flag the exploitation of this issue is that the `namespace` of the CRTB/PRTB will not match the cluster name (`clusterName`) of the CRTB/PRTB. For example, every CRTB in the `c-123xyz` namespace should have a cluster name of `c-123xyz`. If instead, the cluster name is `c-abc567`, for example, this is likely a result of a user exploiting this flaw.\n\nFor more information about cluster and project roles, please consult Rancher's [documentation](https://rancher.com/docs/rancher/v2.6/en/admin-settings/rbac/cluster-project-roles/).\n\n### Patches\n\nPatched versions include releases 2.5.16, 2.6.7 and later versions.\n\n### Workarounds\n\nLimit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.\n\n**Important:**\n- It is highly advised to check the local and downstream clusters for potential unrecognized CRTBs (`kubectl get clusterroletemplatebindings -A`) and PRTBs (`kubectl get projectroletemplatebindings -A`) assignments.\n- The ability to add other users to projects and clusters is a highly-privileged permission which may result in users being able to operate beyond their explicitly specified RBAC. It is recommended that this permission be granted selectively.\n\nThe following script can be used as a helper to detect possible deviations of CRTBs and PRTBs that do not match the expected value. Further investigation is required to determine if the flagged objects were maliciously modified or not. The script requires `kubectl` access to the `local` cluster and the `jq` command.\n\n```shell\n#!/usr/bin/env bash\n\necho \"CRTBs that don't match cluster:\"\nkubectl get clusterroletemplatebindings -A -o=jsonpath=\"{range .items[?(@.clusterName!=@.metadata.namespace)]}{.metadata.name}{'\\n'}{end}\"\n\necho \"PRTBs that don't match project:\"\nkubectl get projectroletemplatebindings -A -ojson | jq -r '.items[]|.metadata as $m|select(.projectName|endswith($m.namespace)|not)|.metadata.name'\n```\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.5.0"
      }, {
        "fixed" : "2.5.16"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.5.15"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.6.0"
      }, {
        "fixed" : "2.6.7"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.6.6"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/security/advisories/GHSA-6x34-89p7-95wg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-31247"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.suse.com/show_bug.cgi?id=1199730"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rancher/rancher"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285", "CWE-863" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-03T14:50:12Z",
    "nvd_published_at" : "2022-09-07T09:15:00Z"
  }
}