CVE-2025-2241

Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm

Description

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.

Remediation

Workaround:

  • 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.

Category

8.2
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.04%
Affected: Red Hat Multicluster Engine for Kubernetes
Affected: Red Hat Red Hat Advanced Cluster Management for Kubernetes 2
Published at:
Updated at:

References

Link Tags
https://access.redhat.com/security/cve/CVE-2025-2241 vdb entry
https://bugzilla.redhat.com/show_bug.cgi?id=2351350 issue tracking

Frequently Asked Questions

What is the severity of CVE-2025-2241?
CVE-2025-2241 has been scored as a high severity vulnerability.
How to fix CVE-2025-2241?
As a workaround for remediating CVE-2025-2241: 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.
Is CVE-2025-2241 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-2241 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-2241?
CVE-2025-2241 affects Red Hat Multicluster Engine for Kubernetes, Red Hat Red Hat Advanced Cluster Management for Kubernetes 2.
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.