Chris Meyers

A flaw was found in the Event-Driven Ansible (EDA) server. The ExternalEventStreamViewSet uses permissive access controls (permission classes=[AllowAny], authentication classes=[]) and relies solely on the Subject HTTP header value for mTLS authentication without verifying that the header originated from a trusted proxy. Additionally, the expected certificate Distinguished Name is leaked in the 403 error response body. An attacker who can reach the EDA API endpoint with a spoofed Subject header can inject arbitrary events into mTLS-protected event streams, triggering downstream automation actions.

**Name of the Vulnerable Software and Affected Versions** Ansible Automation Platform (affected versions not specified) **Description** A flaw in the AAP Gateway Envoy proxy configuration allows an unauthenticated remote attacker to bypass mTLS authentication. The non-mTLS route to EDA event streams fails to remove the `Subject` HTTP header from client requests. By injecting a spoofed `Subject` header that matches a legitimate client certificate Distinguished Name (DN), an attacker can inject arbitrary events into protected EDA event streams. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Event-Driven Ansible (affected versions not specified) **Description** A missing authorization issue exists in the websocket API. The '/api/eda/ws/ansible-rulebook' endpoint fails to verify user permissions when processing Worker messages. This allows any authenticated user to send a forged message containing an arbitrary `activation id` to obtain plaintext credentials associated with that activation, such as OAuth tokens, vault passwords, and SSH keys. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** galaxy ng (affected versions not specified) **Description** A command injection issue exists in the legacy role import API (v1) where the `do git checkout()` function interpolates unsanitized git ref names, such as branch or tag names, into shell commands executed via `subprocess.run()` with `shell=True`. An authenticated user with control over a git repository can use shell metacharacters in a branch or tag name to achieve remote code execution on the pulp worker. This endpoint is only accessible when the `GALAXY ENABLE LEGACY ROLES` variable is set to True. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. Set `GALAXY ENABLE LEGACY ROLES` to False to disable the vulnerable legacy role import API.

**Name of the Vulnerable Software and Affected Versions** Ansible aap-gateway (affected versions not specified) **Description** A flaw was found in the Ansible aap-gateway, where concurrent requests handled by the gateway grpc service can result in concurrency issues due to race condition requests against the proxy. This issue potentially allows a less privileged user to obtain the JWT of a greater privileged user, enabling the server to be jeopardized. A user session or confidential data might be vulnerable. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.