Cri-o: checkpoint restore can be triggered from different namespaces
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.15 | affected |
|
||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.16 | affected |
|
||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.16 | affected |
|
||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.17 | affected |
|
||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.18 | affected |
|
||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4.18 | affected |
|
||||||||||||
| Red Hat | Red Hat Enterprise Linux 8 | unaffected | — | ||||||||||||
| Red Hat | Red Hat Enterprise Linux 8 | affected | — | ||||||||||||
| Red Hat | Red Hat Enterprise Linux 9 | affected | — | ||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 3.11 | unknown | — | ||||||||||||
| Red Hat | Red Hat OpenShift Container Platform 4 | unaffected | — |
No data.
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.15 | |||
| cri-o-0:1.28.11-7.rhaos4.15.gitc4c0556.el8 | cpe:/a:redhat:openshift:4.15::el8 | RHSA-2025:0648 | 2025-01-29T00:00:00Z |
| Red Hat OpenShift Container Platform 4.16 | |||
| cri-o-0:1.29.11-3.rhaos4.16.git16d9bd6.el9 | cpe:/a:redhat:openshift:4.16::el8 | RHBA-2024:10826 | 2024-12-12T00:00:00Z |
| rhcos-416.94.202506251808-0 | cpe:/a:redhat:openshift:4.16::el9 | RHSA-2025:9765 | 2025-07-02T00:00:00Z |
| Red Hat OpenShift Container Platform 4.17 | |||
| rhcos-417.94.202503241418-0 | cpe:/a:redhat:openshift:4.17::el9 | RHSA-2025:3297 | 2025-04-03T00:00:00Z |
| Red Hat OpenShift Container Platform 4.18 | |||
| cri-o-0:1.31.5-5.rhaos4.18.git6dfa0a6.el8 | cpe:/a:redhat:openshift:4.18::el8 | RHSA-2025:1908 | 2025-03-04T00:00:00Z |
| rhcos-418.94.202504231329-0 | cpe:/a:redhat:openshift:4.18::el9 | RHSA-2025:4211 | 2025-05-01T00:00:00Z |
No data available yet.
Vendor 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.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-3348 | 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. |
Github GHSA |
GHSA-7p9f-6x8j-gxxp | CRI-O: Maliciously structured checkpoint file can gain arbitrary node access |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.750% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/o:redhat:enterprise_linux:9 |
cpe:/a:redhat:enterprise_linux:8 cpe:/a:redhat:enterprise_linux:9 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift:4.17::el9 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift:4.18::el8 cpe:/a:redhat:openshift:4.18::el9 |
|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift:4.15::el8 cpe:/a:redhat:openshift:4.15::el9 |
|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift:4.16::el9 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift:4.16::el8 |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Cri-o: checkpoint restore can be triggered from different namespaces | |
| First Time appeared |
Redhat
Redhat enterprise Linux Redhat openshift |
|
| Weaknesses | CWE-285 | |
| CPEs | cpe:/a:redhat:openshift:3.11 cpe:/a:redhat:openshift:4 cpe:/o:redhat:enterprise_linux:8 cpe:/o:redhat:enterprise_linux:9 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux Redhat openshift |
|
| References |
| |
| Metrics |
cvssV3_1
|