fkie_cve-2024-9779
Vulnerability from fkie_nvd
Published
2024-12-17 23:15
Modified
2024-12-17 23:15
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
Summary
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
secalert@redhat.comhttps://access.redhat.com/security/cve/CVE-2024-9779
secalert@redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2317916
secalert@redhat.comhttps://github.com/open-cluster-management-io/ocm/pull/325
secalert@redhat.comhttps://github.com/open-cluster-management-io/ocm/releases/tag/v0.13.0
secalert@redhat.comhttps://github.com/open-cluster-management-io/registration-operator/issues/361
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "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.",
      },
      {
         lang: "es",
         value: "Se encontró una falla en Open Cluster Management (OCM) cuando un usuario tiene acceso a los nodos de trabajo que contienen las implementaciones de cluster-manager o klusterlet. La implementación de cluster-manager utiliza una cuenta de servicio con el mismo nombre \"cluster-manager\" que está vinculada a un ClusterRole también llamado \"cluster-manager\", que incluye el permiso para crear recursos de pod. Si esta implementación ejecuta un pod en un nodo controlado por un atacante, este puede obtener el token de cluster-manager y robar cualquier token de cuenta de servicio mediante la creación y el montaje de la cuenta de servicio de destino para controlar todo el clúster.",
      },
   ],
   id: "CVE-2024-9779",
   lastModified: "2024-12-17T23:15:05.603",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 7.5,
               baseSeverity: "HIGH",
               confidentialityImpact: "LOW",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "CHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.2,
            impactScore: 4.7,
            source: "secalert@redhat.com",
            type: "Primary",
         },
      ],
   },
   published: "2024-12-17T23:15:05.603",
   references: [
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/security/cve/CVE-2024-9779",
      },
      {
         source: "secalert@redhat.com",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2317916",
      },
      {
         source: "secalert@redhat.com",
         url: "https://github.com/open-cluster-management-io/ocm/pull/325",
      },
      {
         source: "secalert@redhat.com",
         url: "https://github.com/open-cluster-management-io/ocm/releases/tag/v0.13.0",
      },
      {
         source: "secalert@redhat.com",
         url: "https://github.com/open-cluster-management-io/registration-operator/issues/361",
      },
   ],
   sourceIdentifier: "secalert@redhat.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-501",
            },
         ],
         source: "secalert@redhat.com",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.