Critical security flaws affect RHACM and MCE console component in environments in which an HTTP proxy is being used

Solution Verified - Updated -

Issue

  • A flaw was found in vm2 where the component was not properly handling asynchronous errors. This flaw allows a remote, unauthenticated attacker to escape the restrictions of the sandbox and execute code on the host. (CVE-2023-29017)

  • A flaw was found in the vm2 sandbox. When exception handling is triggered, the sanitization logic is not managed with proper exception handling. This issue may allow an attacker to bypass the sandbox protections which can lead to remote code execution on the hypervisor host or the host which is running the sandbox. (CVE-2023-29199)

  • A flaw was found in the vm2 sandbox. When exception handling is triggered, an unsanitized host is not managed properly. This issue may allow an attacker to bypass the sandbox protections, which can lead to remote code execution on the hypervisor host or the host that is running the sandbox. (CVE-2023-30547)

  • These issues affect the console components of RHACM and the underlying MCE on hub clusters and pose a risk in environments in which an HTTP proxy is being used (either by being configured at the Openshift cluster level, or by being configured at the RHACM or MCE level for the hub). Clusters that are being managed by RHACM as managed clusters are not impacted.

Environment

  • Red Hat Advanced Cluster Management (RHACM), versions (2.5, 2.6, and 2.7)
  • Multicluster Engine (MCE), versions (2.0, 2.1, and 2.2) (installed as a prerequisite by RHACM)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content