Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||
| Red Hat | Multicluster Engine for Kubernetes | affected | — | ||||||
| Red Hat | Red Hat Advanced Cluster Management for Kubernetes 2 | affected | — |
No data.
No data.
No data available yet.
Vendor 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.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-6523 | 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. |
Github GHSA |
GHSA-c339-mwfc-fmr2 | Openshift Hive Exposes VCenter Credentials via ClusterProvision |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.497% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Hive: exposure of vcenter credentials via clusterprovision in hive / mce / acm | |
| First Time appeared |
Redhat
Redhat acm Redhat multicluster Engine |
|
| Weaknesses | CWE-922 | |
| CPEs | cpe:/a:redhat:acm:2 cpe:/a:redhat:multicluster_engine |
|
| Vendors & Products |
Redhat
Redhat acm Redhat multicluster Engine |
|
| References |
| |
| Metrics |
cvssV3_1
|