fkie_cve-2024-8676
Vulnerability from fkie_nvd
Published
2024-11-26 20:15
Modified
2025-04-03 11:15
Severity ?
7.4 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Summary
A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.
References
secalert@redhat.comhttps://access.redhat.com/errata/RHBA-2024:10826
secalert@redhat.comhttps://access.redhat.com/errata/RHSA-2025:0648
secalert@redhat.comhttps://access.redhat.com/errata/RHSA-2025:1908
secalert@redhat.comhttps://access.redhat.com/errata/RHSA-2025:3297
secalert@redhat.comhttps://access.redhat.com/security/cve/CVE-2024-8676
secalert@redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2313842
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.",
      },
      {
         lang: "es",
         value: "Se encontró una vulnerabilidad en CRI-O, donde se le puede solicitar que tome un archivo de punto de control de un contenedor y luego se le puede solicitar que lo restaure. Cuando realiza esa restauración, intenta restaurar los montajes del archivo de restauración en lugar de la solicitud del pod. Como resultado, las validaciones que se ejecutan en la especificación del pod, verificando que el pod tiene acceso a los montajes que especifica, no son aplicables a un contenedor restaurado. Esta falla permite que un usuario malintencionado engañe a CRI-O para que restaure un pod que no tiene acceso a los montajes del host. El usuario necesita acceso al socket kubelet o cri-o para llamar al endpoint de restauración y activar la restauración.",
      },
   ],
   id: "CVE-2024-8676",
   lastModified: "2025-04-03T11:15:40.703",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 7.4,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.2,
            impactScore: 5.2,
            source: "secalert@redhat.com",
            type: "Secondary",
         },
      ],
   },
   published: "2024-11-26T20:15:34.260",
   references: [
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHBA-2024:10826",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHSA-2025:0648",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHSA-2025:1908",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/errata/RHSA-2025:3297",
      },
      {
         source: "secalert@redhat.com",
         url: "https://access.redhat.com/security/cve/CVE-2024-8676",
      },
      {
         source: "secalert@redhat.com",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2313842",
      },
   ],
   sourceIdentifier: "secalert@redhat.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-285",
            },
         ],
         source: "secalert@redhat.com",
         type: "Secondary",
      },
   ],
}


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.