CVE-2024-8676
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.
- Affected products
- Cri-O
- Fix
- Available
- CVSS 3.1
- 7.4 HIGH
- EPSS
- 0.8% (52th percentile)
- Weakness
- CWE-285
- NVD status
- Deferred
- Published
- 2024-11-26
Workaround
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
No indexed exploits for CVE-2024-8676 yet
Our index is partial: it proves presence, never absence
No exploit for CVE-2024-8676 has been indexed yet. Our index is built from live traffic and upstream syncs, so this page can only say what it knows — not that no exploit exists.