Kubernetes YAML Exploit Grants GCP Organization Control

A critical vulnerability has been identified within Google Kubernetes Engine (GKE) that allows a Kubernetes user with limited permissions to gain complete control over an entire Google Cloud organization. Security researchers at Varonis detailed this exploit, which leverages the authority granted to the Google Kubernetes Config Connector, a tool designed to manage Google Cloud resources from within Kubernetes. The exploit functions as a confused deputy problem, where the Config Connector, acting on behalf of a less privileged Kubernetes user, is tricked into performing actions with elevated privileges that it would not normally be permitted to execute.

The core of the exploit lies in the way the Config Connector handles permissions and resource management. When a Kubernetes user creates or modifies a YAML configuration file that instructs the Config Connector to manage a Google Cloud resource, the Config Connector assumes the necessary permissions to fulfill that request. If the YAML file is maliciously crafted, it can instruct the Config Connector to create or modify resources in a way that escalates the initial user's privileges. This escalation can lead to the attacker gaining administrative access to the entire Google Cloud organization, including all projects, data, and services within it.

Varonis's analysis indicates that a single, carefully constructed Kubernetes YAML file is sufficient to initiate this privilege escalation. The exploit bypasses standard security controls by exploiting the trust relationship between Kubernetes and the Google Cloud environment through the Config Connector. This means that an attacker who can deploy even a single malicious YAML file into a Kubernetes cluster that is configured with the Config Connector can potentially compromise the entire cloud infrastructure managed by that organization.

The implications of this vulnerability are significant, as it could allow unauthorized individuals to access, modify, or delete sensitive data, disrupt critical services, or incur substantial costs by provisioning expensive cloud resources. The exploit highlights the importance of stringent access controls and regular security audits for both Kubernetes clusters and their integrated cloud management tools. Organizations using GKE with the Config Connector are advised to review their security configurations and implement measures to prevent the deployment of unauthorized or malicious YAML files. This includes enforcing least privilege principles for Kubernetes users and ensuring that the Config Connector itself is configured with the minimum necessary permissions to perform its intended functions.