A flaw was found in the cluster-curator-controller component. A local user, by creating a ClusterCurator resource with a specific naming convention, can trigger the creation of a cluster-scoped ClusterRoleBinding. This allows the user to escalate their privileges from namespace-local access to cluster-wide control. This privilege escalation grants broad permissions, including the ability to access and manipulate secrets, manage cluster actions, and delete hosted clusters or node pools.
To mitigate this issue, restrict the ability of tenants to create ClusterCurator resources. Implement Kubernetes Role-Based Access Control (RBAC) policies to limit create permissions for clustercurators.cluster.open-cluster-management.io resources to only trusted administrators or service accounts. Alternatively, deploy an admission controller to enforce that metadata.name and metadata.namespace fields are identical when ClusterCurator resources are created, preventing the vulnerable condition.