Advisory

GHSA-j4vr-pcmw-hx59

Also known as: CVE-2023-32199, GO-2025-4073

Summary

Rancher user retains access to clusters despite Global Role removal

Details

Impact
A vulnerability has been identified within Rancher Manager, where after removing a custom GlobalRole that gives administrative access or the corresponding binding, the user still retains access to clusters.
This only affects custom Global Roles that:

  • Have a * on * in * rule for resources
  • Have a * on * rule for non-resource URLs

For example

apiVersion: management.cattle.io/v3
kind: GlobalRole
metadata:
  name: custom-admin
rules:
  - apiGroups:
      - '*'
    resources:
      - '*'
    verbs:
      - '*'
  - nonResourceURLs:
      - '*'
    verbs:
      - '*'

Specifically:

  • When a user is bound to a custom admin GlobalRole, a corresponding ClusterRoleBinding is created on all clusters that binds them to the cluster-admin ClusterRole.
  • When such a GlobalRole or the GlobalRoleBinding (e.g., when the user is unassigned from this role in UI) is deleted, the ClusterRoleBinding that binds them to the cluster-admin ClusterRole stays behind.

This issue allows a user to continue having access to clusters after they have been unassigned from the custom admin global role or the role has been deleted.

Please consult the associated MITRE ATT&CK - Technique - Account Access Removal for further information about this category of attack.

Patches
This vulnerability is addressed by removing the corresponding ClusterRoleBindings whenever the admin GlobalRole or its GlobalRoleBindings are deleted. Previously orphaned ClusterRoleBindings are marked with the annotation authz.cluster.cattle.io/admin-globalrole-missing=true and should be deleted manually.

Orphaned ClusterRoleBindings can be listed with:

kubectl get clusterrolebinding -o jsonpath='{range .items[?(@.metadata.annotations.authz\.cluster\.cattle\.io/admin-globalrole-missing=="true")]}{.metadata.name}{"\n"}{end}'

Patched versions of Rancher include releases v2.12.3, v2.11.7.

Complications with the restricted admin functionality prevented the patches from being included in v2.10 and v2.9.

Workarounds
If the deployment can't be upgraded to a fixed version, users are advised to manually identify the orphaned ClusterRoleBindings and remove them.

References
If you have any questions or comments about this advisory:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-10-24 15:06 UTC
Modified
2025-11-05 19:57 UTC

Affected packages and fixes

github.com/rancher/rancher

Go · All systems

Affected

  • introduced 0, fixed 0.0.0-20251014212116-7faa74a968c2 (semver)

Fixed versions

0.0.0-20251014212116-7faa74a968c2

Fix

  • Fixed version 0.0.0-20251014212116-7faa74a968c2
    go get github.com/rancher/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences