CVE-2024-8676: CRI-O: Maliciously structured checkpoint file can gain arbitrary node access
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
- access.redhat.com/security/cve/CVE-2024-8676
- bugzilla.redhat.com/show_bug.cgi?id=2313842
- github.com/advisories/GHSA-7p9f-6x8j-gxxp
- github.com/cri-o/cri-o
- github.com/cri-o/cri-o/commit/e8e7dcb7838d11b5157976bf3e31a5840bb77de7
- github.com/cri-o/cri-o/security/advisories/GHSA-7p9f-6x8j-gxxp
- nvd.nist.gov/vuln/detail/CVE-2024-8676
Detect and mitigate CVE-2024-8676 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →