Two management-plane actions hand you the cluster. listClusterAdminCredential returns a cluster-admin kubeconfig that bypasses Azure RBAC entirely, and managedClusters runCommand runs kubectl (or any command) inside the cluster from the Azure side, which works even when the API server is private.
Pull the admin kubeconfig#
# admin creds ignore Azure AD / RBAC integration
az aks get-credentials -g <rg> -n <cluster> --admin
kubectl get secrets -A
Run commands through the management plane#
az aks command invoke -g <rg> -n <cluster> \
-c "kubectl get secrets -A -o json"
Exploitation notes#
--adminrequires thelistClusterAdminCredentialaction; it is the single most valuable AKS right because it sidesteps any Azure-AD cluster RBAC.command invokereaches a private cluster with no network line of sight, since it runs through the Azure control plane.- Cluster secrets routinely include further cloud credentials and service-account tokens for lateral movement.
Tools#
- Azure CLI (
az aks get-credentials --admin,az aks command invoke). - kubectl / Peirates: in-cluster enumeration and movement once you hold the kubeconfig.