open-cluster-management: Open-Cluster-Management: Privilege escalation and unauthorized resource modification in gRPC broker
No data.
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Open Business Management | Open Business Management |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Open Business Management
Open Business Management open Business Management |
|
| Vendors & Products |
Open Business Management
Open Business Management open Business Management |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in open-cluster-management. An agent communicating via the gRPC broker can bypass authorization by manipulating the `ce-clustername` cloud event header attribute, which is used for authorization, independently of the actual event payload. This allows a registered managed cluster to gain unauthorized access, enabling it to move itself into other tenants' ManagedClusterSets and overwrite other clusters' ManagedCluster objects in the hub. The primary consequence is a breach of isolation between managed clusters, leading to unauthorized modification of cluster resources. This can lead to unauthorized receipt of newly delivered tenant workloads, policies, and secrets via Placement decisions. Additionally, an attacker can arbitrarily overwrite other clusters' ManagedCluster objects on the hub or perform unauthorized writes inside another cluster's dedicated hub namespace, such as forging Lease liveness heartbeats to manipulate availability status. | |
| Title | open-cluster-management: Open-Cluster-Management: Privilege escalation and unauthorized resource modification in gRPC broker | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|