High [CVE-2025-2241] Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm
This high-severity Red Hat Linux advisory covers CVE-2025-2241 affecting Multicluster Engine for Kubernetes, Red Hat Advanced Cluster Management for Kubernetes 2.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Hive, a component of Multicluster Engine (MCE) and Advanced Cluster Management (ACM). This vulnerability causes VCenter credentials to be exposed in the ClusterProvision object after provisioning a VSphere cluster.
Users with read access to ClusterProvision objects can extract sensitive credentials even if they do not have direct access to Kubernetes Secrets. This issue can lead to unauthorized VCenter access, cluster management, and privilege escalation.
Hive is an operator which runs as a service for provisioning and perform initial configuration of OpenShift clusters. During this process users are creating instances of hive CRDs and other k8s objects, including a Secret containing credentials where Hive take these inputs and invokes openshift-install to create the spoke cluster.
One of these objects is an instance of a hive CRD called ClusterProvision. The ClusterProvision object contains unintentionally sensitive information, which may be accessed by unauthorized actors.
Red Hat severity: Important — CVSS 8.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N). Weakness: CWE-922.
Affected Red Hat products: Multicluster Engine for Kubernetes; Red Hat Advanced Cluster Management for Kubernetes 2. Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 21 minutes ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 21 minutes ago·verify at source
Mitigation checklist
- A few mechanisms are available to reduce the risks and mitigate this vulnerability: 1. Restrict Access to ClusterProvision Objects Ensure that only trusted users with valid VCenter credentials have read access to ClusterProvision objects. This can be verified using the following commands: oc adm policy who-can get clusterprovision oc adm policy who-can read clusterprovision 2. Rotate VCenter Credentials Immediately rotate VCenter credentials to revoke access for any users who may have already accessed the exposed credentials. 3. Audit VCenter Users and Roles Conduct a security audit of VCenter accounts and roles to detect any unauthorized access or configuration changes. If any suspicious activity is found, revoke access by rotating credentials again (step 2) and taking necessary remediation actions.
Official advisory · high-confidence parse· fetched 21 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.