Knowledge Base · general

Kubernetes & Cloud IAM Abuse

generaltechnique notetechniquekubernetes-iam

Privilege escalation through RBAC, role-binding self-modification, workload service accounts and stale cloud credentials.

How it works

  • A low-privilege identity that can create/modify role bindings can grant itself more rights.
  • Create a workload that runs as a more privileged service account, then read its token from logs.
  • Stale ‘external ID’ / cached credentials are a decoy for the live ones.

Detection & defence

  • Apply least privilege; do not let principals modify their own bindings.
  • Keep service-account tokens out of logs; scope cloud role assumption tightly.