CVE-2024-8676
A vulnerability was found in CRI-O, where it can be requested to …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- access.redhat.com/errata/RHBA-2024:10826
- access.redhat.com/errata/RHSA-2025:0648
- access.redhat.com/errata/RHSA-2025:1908
- access.redhat.com/errata/RHSA-2025:3297
- access.redhat.com/errata/RHSA-2025:4211
- access.redhat.com/errata/RHSA-2025:9765
- access.redhat.com/security/cve/CVE-2024-8676
- bugzilla.redhat.com/show_bug.cgi?id=2313842
- nvd.nist.gov/vuln/detail/CVE-2024-8676
- cve.org/CVERecord?id=CVE-2024-8676
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.