Cri-o: checkpoint restore can be triggered from different namespaces
Summary
| CVE | CVE-2024-8676 |
|---|---|
| State | PUBLISHED |
| Assigner | redhat |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2024-11-26 20:15:34 UTC |
| Updated | 2026-10-13 03:16:38 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.4 HIGH from [email protected]
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS: 0.007730000 probability, percentile 0.529430000 (date 2026-08-24)
Problem Types: CWE-285 | CWE-285 Improper Authorization
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 7.4 | HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| 3.1 | CNA | CVSS | 7.4 | HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.15 | unaffected 0:1.28.11-7.rhaos4.15.gitc4c0556.el8 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.16 | unaffected 0:1.29.11-3.rhaos4.16.git16d9bd6.el8 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.16 | unaffected 416.94.202506251808-0 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.17 | unaffected 417.94.202503241418-0 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.18 | unaffected 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8 * rpm | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4.18 | unaffected 418.94.202504231329-0 * rpm | Not specified |
| CNA | Red Hat | Red Hat Enterprise Linux 8 | Not specified | Not specified |
| CNA | Red Hat | Red Hat Enterprise Linux 8 | Not specified | Not specified |
| CNA | Red Hat | Red Hat Enterprise Linux 9 | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 3.11 | Not specified | Not specified |
| CNA | Red Hat | Red Hat OpenShift Container Platform 4 | Not specified | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| access.redhat.com/errata/RHSA-2025:4211 | [email protected] | access.redhat.com | |
| access.redhat.com/errata/RHSA-2025:9765 | [email protected] | access.redhat.com | |
| access.redhat.com/errata/RHSA-2025:3297 | [email protected] | access.redhat.com | |
| access.redhat.com/errata/RHSA-2025:1908 | [email protected] | access.redhat.com | |
| bugzilla.redhat.com/show_bug.cgi | [email protected] | bugzilla.redhat.com | |
| access.redhat.com/errata/RHSA-2025:0648 | [email protected] | access.redhat.com | |
| access.redhat.com/security/cve/CVE-2024-8676 | [email protected] | access.redhat.com | |
| access.redhat.com/errata/RHBA-2024:10826 | [email protected] | access.redhat.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
| Source | Time | Event |
|---|---|---|
| CNA | 2024-09-20T19:45:05.331Z | Reported to Red Hat. |
| CNA | 2024-11-26T18:21:38.116Z | Made public. |
Workarounds
CNA: 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.
There are currently no legacy QID mappings associated with this CVE.