Описание
Open Cluster Management vulnerable to Trust Boundary Violation
A flaw was found in Open Cluster Management (OCM) when a user has access to the worker nodes which contain the cluster-manager or klusterlet deployments. The cluster-manager deployment uses a service account with the same name "cluster-manager" which is bound to a ClusterRole also named "cluster-manager", which includes the permission to create Pod resources. If this deployment runs a pod on an attacker-controlled node, the attacker can obtain the cluster-manager's token and steal any service account token by creating and mounting the target service account to control the whole cluster.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2024-9779
- https://github.com/open-cluster-management-io/registration-operator/issues/361
- https://github.com/open-cluster-management-io/ocm/pull/325
- https://access.redhat.com/security/cve/CVE-2024-9779
- https://bugzilla.redhat.com/show_bug.cgi?id=2317916
- https://github.com/open-cluster-management-io/ocm/releases/tag/v0.13.0
Пакеты
open-cluster-management.io/ocm
< 0.13.0
0.13.0
Связанные уязвимости
A flaw was found in Open Cluster Management (OCM) when a user has access to the worker nodes which contain the cluster-manager or klusterlet deployments. The cluster-manager deployment uses a service account with the same name "cluster-manager" which is bound to a ClusterRole also named "cluster-manager", which includes the permission to create Pod resources. If this deployment runs a pod on an attacker-controlled node, the attacker can obtain the cluster-manager's token and steal any service account token by creating and mounting the target service account to control the whole cluster.
A flaw was found in Open Cluster Management (OCM) when a user has access to the worker nodes which contain the cluster-manager or klusterlet deployments. The cluster-manager deployment uses a service account with the same name "cluster-manager" which is bound to a ClusterRole also named "cluster-manager", which includes the permission to create Pod resources. If this deployment runs a pod on an attacker-controlled node, the attacker can obtain the cluster-manager's token and steal any service account token by creating and mounting the target service account to control the whole cluster.
