{"uuid": "8cf4a80f-1acb-4053-a3a7-c048c9d3fce5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "RHSA-2025:0648", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/6398", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-8676\n\ud83d\udd25 CVSS Score: 7.4 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2024-11-26T19:15:48.475Z\n\ud83d\udccf Modified: 2025-03-04T18:20:24.881Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHBA-2024:10826\n2. https://access.redhat.com/errata/RHSA-2025:0648\n3. https://access.redhat.com/errata/RHSA-2025:1908\n4. https://access.redhat.com/security/cve/CVE-2024-8676\n5. https://bugzilla.redhat.com/show_bug.cgi?id=2313842", "creation_timestamp": "2025-03-04T18:32:39.000000Z"}