The vulnerability in Red Hat Ansible Automation Platform 2's automation-controller exposes the provisioning-callback secret (host_config_key) to users with view_jobtemplate permission. The provisioning callback endpoint trusts the client-supplied X-Forwarded-For header to determine the calling host if the controller is behind the AAP gateway with an empty PROXY_IP_ALLOWED_LIST. An attacker can read the secret and spoof the X-Forwarded-For header to impersonate any host in the job template's inventory, enabling them to launch job templates against arbitrary managed hosts using the job template's credentials. This results in privilege escalation and remote code execution on those hosts. The issue affects versions 2.5, 2.6, and 2.7 of the platform where the gateway/envoy topology was introduced. The host_config_key exposure exists independently of version, but the full exploit chain requires the gateway topology with an empty proxy allow-list.

An attacker with minimal privileges or no authentication can obtain sensitive secrets and spoof host identities to execute arbitrary job templates on managed hosts. This leads to privilege escalation and remote code execution, compromising confidentiality, integrity, and availability of affected systems. The CVSS v3.1 score is 9.9, indicating critical severity with network attack vector, low complexity, low privileges required, no user interaction, and scope change.

Red Hat recommends restricting the view_jobtemplate permission on job templates with provisioning callback enabled and disabling provisioning callback (clearing host_config_key) on job templates that do not require it. Administrators should configure PROXY_IP_ALLOWED_LIST to include only trusted AAP gateway or envoy addresses to prevent untrusted X-Forwarded-For headers from being accepted. Any host_config_key values potentially exposed to read-only users should be rotated. Monitoring for jobs launched with launch_type=callback and unexpected parameters is advised. These mitigations reduce risk until an official fix is available. Patch status is not explicitly stated; check the Red Hat advisory for updates.