CyberRota Analysis
AI-GeneratedA server-side request forgery (SSRF) vulnerability in AWX's webhook status callback mechanism allows an attacker with admin access to a webhook-enabled job template to manipulate the status callback URL. This exploitation can lead to unauthorized status updates being sent to an attacker-controlled endpoint, resulting in the leakage of sensitive credentials, including the Git Personal Access Token. Organizations using AWX with GitHub integrations should prioritize addressing this vulnerability to mitigate the risk of credential exposure.
Original NVD Description
A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected Git provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured Git Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.