Skip to content

Open Cluster Management vulnerable to Trust Boundary Violation

High severity GitHub Reviewed Published Dec 18, 2024 to the GitHub Advisory Database • Updated Dec 18, 2024

Package

gomod open-cluster-management.io/ocm (Go)

Affected versions

< 0.13.0

Patched versions

0.13.0

Description

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

Published by the National Vulnerability Database Dec 17, 2024
Published to the GitHub Advisory Database Dec 18, 2024
Reviewed Dec 18, 2024
Last updated Dec 18, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

EPSS score

0.054%
(25th percentile)

Weaknesses

CVE ID

CVE-2024-9779

GHSA ID

GHSA-jhh6-6fhp-q2xp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.