CVE-2025-11393
Privilege Escalation via Misconfigured Proxy in Runtimes-Inventory-RHEL8 Operator
Publication date: 2025-12-15
Last updated on: 2025-12-16
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| redhat | runtimes-inventory-rhel8-operator | 3.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-441 | The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is caused by an internal proxy component in the runtimes-inventory-rhel8-operator being incorrectly configured. Instead of attaching the cluster's main administrative credentials only to specific reports it should handle, the proxy attaches these credentials to any command it receives. This means that any standard user within the cluster can send unauthorized commands to the management platform and act with full cluster administrator privileges. [1]
How can this vulnerability impact me? :
Because of this vulnerability, a standard user in the cluster can execute unauthorized administrative commands on the management platform. This could lead to unauthorized changes to the cluster's configuration or status, potentially compromising the security and stability of the Red Hat platform environment. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade from Red Hat Insights for Runtimes on RHEL 8 container images to the updated RHEL 9 container images that include backported patches correcting this issue. Additionally, rebuild all dependent container images after applying the update. Ensure all prior relevant errata are applied before updating. [1]