CVE-2024-8676

{"id": "CVE-2024-8676", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "published": "2024-11-26T20:15:34.260", "references": [{"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/security/cve/CVE-2024-8676", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "source": "secalert@redhat.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-285"}]}], "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\u00f3 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\u00f3n, intenta restaurar los montajes del archivo de restauraci\u00f3n en lugar de la solicitud del pod. Como resultado, las validaciones que se ejecutan en la especificaci\u00f3n 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\u00f1e 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\u00f3n y activar la restauraci\u00f3n."}], "lastModified": "2025-03-04T19:15:37.457", "sourceIdentifier": "secalert@redhat.com"}