rbac-audit

Audits Kubernetes RBAC exports for cluster-admin grants, wildcard roles, secret readers, exec rights and privilege escalation verbs. Crystal.

3 files, 12 findings

SeverityRuleWhereFinding
criticalRBAC008prod-cluster.json:ClusterRoleBinding/anon-secretsUser system:anonymous is bound to secret-reader: anyone on the network gets these rights
criticalRBAC001prod-cluster.json:ClusterRoleBinding/everyone-adminGroup system:authenticated is bound to cluster-admin
highRBAC004prod-cluster.json:ClusterRole/debuggercan open a shell or attach inside pods or proxy to nodes: pods/exec
highRBAC005prod-cluster.json:ClusterRole/debuggerverbs that bypass RBAC checks: bind, escalate
highRBAC002prod-cluster.json:ClusterRole/dev-allwildcard verbs on wildcard resources: this role is cluster-admin in all but name
highRBAC003prod-cluster.json:ClusterRole/secret-readercan read secrets in every namespace
highRBAC001prod-cluster.json:ClusterRoleBinding/ci-adminServiceAccount ci/jenkins is bound to cluster-admin
mediumRBAC006prod-cluster.json:ClusterRole/debuggercan create or change roles and bindings: a path to more privilege
mediumRBAC001prod-cluster.json:ClusterRoleBinding/ci-adminUser alice@example.test is bound to cluster-admin
mediumRBAC003prod-cluster.json:Role/shop/cm-readercan read secrets
mediumRBAC007prod-cluster.json:RoleBinding/shop/default-editthe default service account of shop is bound to edit: every pod without its own account inherits it
infoRBAC000other.jsonno Role, ClusterRole, RoleBinding or ClusterRoleBinding found

Synthetic cluster exports. This page is rendered from the tool's --tsv output by scripts/site.py.