Checkpoint restore can be triggered from different namespaces
CVE: CVE-2024-8676
Component: cri-o
CWE: CWE-285
Severity: Moderate
CVSS v3: 7.4/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Release date: 2024-11-26T18:21:38.116000+00:00

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.


Remediation:
For OpenShift Container Platform 4.15 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.openshift.com/container-platform/4.15/release_notes/ocp-4-15-release-notes.html
See the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.openshift.com/container-platform/4.16/release_notes/ocp-4-16-release-notes.html

Details on how to access this content are available at
https://docs.openshift.com/container-platform/4.16/updating/updating-cluster-cli.html
For OpenShift Container Platform 4.18 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.openshift.com/container-platform/4.18/release_notes/ocp-4-18-release-notes.html
For OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/release_notes/

You may download the oc tool and use it to inspect release image metadata
for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests
may be found at
https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags.

The sha values for the release are as follows:

      (For x86_64 architecture)
      The image digest is sha256:8597a1a05b1792619cf56734de97fabe5f7ff77a100060924b4f5740ec10f2e1

      (For s390x architecture)
      The image digest is sha256:379c66f3c9f8aac11cdaa74614fd8d2b2c8a4626c3604f641d2ea7ee0d46be70

      (For ppc64le architecture)
      The image digest is sha256:5a5897081b628d1330e7d23dd3bd3de71cb647152fb1ed3a4fc10a85c4265ce1

      (For aarch64 architecture)
      The image digest is sha256:235fd4e1df9a004001768ee48ff44d102634c08b789cc37a329ad6a52f6ce13a

All OpenShift Container Platform 4.16 users are advised to upgrade to these
updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at
https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/updating_clusters/index#updating-cluster-cli.
For OpenShift Container Platform 4.17 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/release_notes/

You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags.

The sha values for the release are as follows:

      (For x86_64 architecture)
      The image digest is sha256:7e8b4557c0a15765440c543ab50cd591bb94f0745c20564e5f15d57bf5f76a82

      (For s390x architecture)
      The image digest is sha256:dd3148c37d8b4122f500ae1bb92e29e34d1cc3bfa634d5c53a9f8528945abd2d

      (For ppc64le architecture)
      The image digest is sha256:04bf2f5c15417eeb7de26d95de767b62ce263d5cc99400cbaa4d370c5007ab18

      (For aarch64 architecture)
      The image digest is sha256:b491dcca8f5a2fe177f628f661a23086497440cf9b994638b199b9299335741b

All OpenShift Container Platform 4.17 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html-single/updating_clusters/index#updating-cluster-cli.
For OpenShift Container Platform 4.18 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/release_notes/

You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags.

The sha values for the release are as follows:

      (For x86_64 architecture)
      The image digest is sha256:b3c76706606940d84964095aaab1a8ed4eca0d1bd6833b4eb718115842ef6850

      (For s390x architecture)
      The image digest is sha256:ba245bfdba7d81161971640e255f334e20b281ef15342dbf2587504bd30d3a94

      (For ppc64le architecture)
      The image digest is ha256:749484f20536a9a75ce57e4fafd57f6216e596256ed2f712a769ebb3e7c785f4

      (For aarch64 architecture)
      The image digest is sha256:b5c055b54ca8581f11a3acfd72bcace0319f6f9aca35f834996fa579b6543dd9

All OpenShift Container Platform 4.18 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/updating_clusters/index#updating-cluster-cli.
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.