The vulnerability exists in the kubernetes_auth() function of the awx_plugins/credentials/hashivault.py file within the AAP Controller's HashiCorp Vault credential plugin. When a HashiCorp Vault Secret Lookup credential configured with kubernetes_role authentication is tested, the function reads the Kubernetes service account token of the controller pod and sends it to an attacker-controlled URL. An attacker with credential-creation privileges can exploit this to exfiltrate the token, thereby gaining unauthorized Kubernetes API access with extensive permissions, including the ability to create, read, update, and delete pods and secrets in control plane namespaces. This includes access to sensitive secrets such as database credentials and the Django SECRET_KEY. The vulnerability is present in all versions of AAP shipping the hashivault plugin with kubernetes_role support, affecting both on-premise and cloud deployments, with higher impact in cloud environments due to tenant isolation concerns.

An authenticated attacker with credential-creation privileges can exfiltrate the Kubernetes service account token from the controller pod. This token grants the attacker Kubernetes API access to control plane namespaces with full pod CRUD and secret read permissions. Sensitive information such as database credentials and the Django SECRET_KEY can be accessed, potentially compromising the confidentiality and integrity of the environment. The vulnerability is critical due to the high privileges gained and the potential for widespread impact in managed cloud environments where tenant isolation is a key security boundary.

Red Hat has not explicitly stated that a fix is available yet. Until a fix is released, mitigation involves restricting network egress from controller pods using Kubernetes NetworkPolicy to prevent outbound connections to untrusted destinations, allowing only known Vault server endpoints. Review and restrict RBAC permissions of the automation-controller service account to enforce least privilege and remove unnecessary secret read access. In cloud environments, audit credential-creation activities for suspicious Vault credentials with external or unusual URLs. Monitor Kubernetes audit logs for unexpected API calls by the automation-controller service account, especially secret reads and pod operations. Rotate the automation-controller service account token if unauthorized access is suspected. Consider limiting the 'create credential' privilege to trusted administrators until a fix is available. Check the Red Hat advisory for updates on patch availability.