Aap-gateway: aap-gateway privilege escalation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 8 | affected |
|
||||||
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 9 | affected |
|
No data.
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | |||
| automation-gateway-0:2.5.20250305-1.el8ap | cpe:/a:redhat:ansible_automation_platform:2.5::el8 | RHSA-2025:1954 | 2025-03-01T00:00:00Z |
| Red Hat Ansible Automation Platform 2.5 for RHEL 9 | |||
| automation-gateway-0:2.5.20250305-1.el9ap | cpe:/a:redhat:ansible_automation_platform:2.5::el9 | RHSA-2025:1954 | 2025-03-01T00:00:00Z |
No data available yet.
Vendor Workaround
Follow the mitigation steps to avoid the flaw from happening. It is recommended to update the product after the fix is available. 1) set GRPC_SERVER_MAX_THREADS_PER_PROCESS = 1 This mitigates problems going FORWARD for the issue because there is only one thread using the ExternalAuth() object instantiated by the parent process. This eliminates the thread safety risk as the worker only processes one request at a time. 2) It is possible that at any time since the install/upgrade of AAP 2.5, that long lived Oauth tokens created in the components with the endpoints could implicate long term access to a different user's identity/privileges. Requests made with these tokens will appear to be from the user for which they were created and are indistinguishable from “valid” tokens that were created by the correct user: /api/controller/v2/tokens/ /api/controller/v2/applications/<id>/tokens/ /api/galaxy/v3/auth/token/ /api/controller/o/token/ Because it is likely not feasible to back trace every request that could have generated a token to its original request in the GRPC server, the most conservative and safe path to mitigate this risk would be to invalidate/revoke all existing oauth tokens in the components (hub, controller, eda).
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-5589 | A flaw was found in the Ansible aap-gateway. 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.327% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | No description is available for this CVE. | A flaw was found in the Ansible aap-gateway. 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. |
| Title | aap-gateway: aap-gateway privilege escalation | Aap-gateway: aap-gateway privilege escalation |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | No description is available for this CVE. | |
| Title | aap-gateway: aap-gateway privilege escalation | |
| First Time appeared |
Redhat
Redhat ansible Automation Platform |
|
| Weaknesses | CWE-362 | |
| CPEs | cpe:/a:redhat:ansible_automation_platform:2.5::el8 cpe:/a:redhat:ansible_automation_platform:2.5::el9 |
|
| Vendors & Products |
Redhat
Redhat ansible Automation Platform |
|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|