CVE-2024-9779: 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.
References
- access.redhat.com/security/cve/CVE-2024-9779
- bugzilla.redhat.com/show_bug.cgi?id=2317916
- github.com/advisories/GHSA-jhh6-6fhp-q2xp
- github.com/open-cluster-management-io/OCM
- github.com/open-cluster-management-io/ocm/pull/325
- github.com/open-cluster-management-io/ocm/releases/tag/v0.13.0
- github.com/open-cluster-management-io/registration-operator/issues/361
- nvd.nist.gov/vuln/detail/CVE-2024-9779
Code Behaviors & Features
Detect and mitigate CVE-2024-9779 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →