CVE-2025-1801

Aap-gateway: aap-gateway privilege escalation

Description

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.

Remediation

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//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).

Category

8.1
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.04%
Vendor Advisory redhat.com
Affected: 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
Published at:
Updated at:

References

Link Tags
https://access.redhat.com/errata/RHSA-2025:1954 vendor advisory
https://access.redhat.com/security/cve/CVE-2025-1801 vdb entry
https://bugzilla.redhat.com/show_bug.cgi?id=2349081 issue tracking

Frequently Asked Questions

What is the severity of CVE-2025-1801?
CVE-2025-1801 has been scored as a high severity vulnerability.
How to fix CVE-2025-1801?
As a workaround for remediating CVE-2025-1801: 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//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).
Is CVE-2025-1801 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-1801 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-1801?
CVE-2025-1801 affects Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.