Skip to content
Fencer Vulns
high 7.4

CVE-2024-8676 json

Cri-o: checkpoint restore can be triggered from different namespaces

published 2024-11-26 23 mo ago modified 2026-11-05 3 d ago also GHSA-7p9f-6x8j-gxxp , GO-2024-3292 , EUVD-2024-3348

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/cri-o/cri-o 1.29.11, 1.30.8, 1.31.3
  • Red Hat Red Hat OpenShift Container Platform 4.15 0:1.28.11-7.rhaos4.15.gitc4c0556.el8
  • Red Hat Red Hat OpenShift Container Platform 4.16 0:1.29.11-3.rhaos4.16.git16d9bd6.el8, 416.94.202506251808-0
  • Red Hat Red Hat OpenShift Container Platform 4.17 417.94.202503241418-0
  • Red Hat Red Hat OpenShift Container Platform 4.18 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8, 418.94.202504231329-0
  • cri-o openshift 4.18 1.31.5-5.rhaos4.18.git6dfa0a6.el8
  • cri-o openshift 4.18 1.31.5-5.rhaos4.18.git6dfa0a6.el9
  • buildah openshift 4.18 2:1.33.12-1.rhaos4.18.el9
  • buildah-tests openshift 4.18 2:1.33.12-1.rhaos4.18.el9
  • cri-o openshift 4.15 1.28.11-7.rhaos4.15.gitc4c0556.el8
  • cri-o openshift 4.15 1.28.11-7.rhaos4.15.gitc4c0556.el9
  • cri-o openshift 4.16 1.29.11-3.rhaos4.16.git16d9bd6.el8
  • cri-o openshift 4.16 1.29.11-3.rhaos4.16.git16d9bd6.el9

red hat advisories RHSA-2025:1908RHSA-2025:0648RHBA-2024:10826

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20241209T183251-1.1

opensuse advisories openSUSE-SU-2024:14567-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-8676 updated cvss 7.4

cri-o: Checkpoint restore can be triggered from different namespaces

  • Red Hat Enterprise Linux 8 podman, podman-tests, podman-docker, podman-remote, podman-gvproxy, podman-plugins, +2 more
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Enterprise Linux 9 conmon
    affected: workaround, no fix available
  • Red Hat OpenShift Container Platform 3.11 cri-o
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat OpenShift Container Platform 4.15 cri-o 1.28.11-7.rhaos4.15.gitc4c0556.el8, cri-o 1.28.11-7.rhaos4.15.gitc4c0556.el9
    fixed: vendor fix RHSA-2025:0648
  • Red Hat OpenShift Container Platform 4.16 rhcos 416.94.202506251808-0, cri-o 1.29.11-3.rhaos4.16.git16d9bd6.el8, cri-o 1.29.11-3.rhaos4.16.git16d9bd6.el9
    fixed: vendor fix RHBA-2024:10826
  • Red Hat OpenShift Container Platform 4.17 rhcos 417.94.202503241418-0
    fixed: vendor fix RHSA-2025:3297
  • Red Hat OpenShift Container Platform 4.18 rhcos 418.94.202504231329-0, cri-o 1.31.5-5.rhaos4.18.git6dfa0a6.el8, cri-o 1.31.5-5.rhaos4.18.git6dfa0a6.el9
    fixed: vendor fix RHSA-2025:1908
  • Red Hat Enterprise Linux 8 conmon Red Hat OpenShift Container Platform 4 conmon Red Hat OpenShift Container Platform 4.16 openshift4/ose-cli-rhel9 v4.16.0-202506062300.p0.gee354f6.assembly.stream.el9, openshift4/ose-pod-rhel9 v4.16.0-202506251307.p0.g29b5494.assembly.stream.el9, openshift4/ose-sdn-rhel9 v4.16.0-202506202104.p0.g53fea06.assembly.stream.el9, openshift4/ose-etcd-rhel9 v4.16.0-202506062300.p0.ge7911c0.assembly.stream.el9, openshift4/ose-tests-rhel9 v4.16.0-202506250035.p0.g65d2ed0.assembly.stream.el9, openshift4/ose-tools-rhel9 v4.16.0-202506250035.p0.gee354f6.assembly.stream.el9, +185 more Red Hat OpenShift Container Platform 4.17 openshift4/frr-rhel9 v4.17.0-202503251509.p0.gc30988b.assembly.stream.el9, openshift4/ose-cli-rhel9 v4.17.0-202503210032.p0.g0000b3e.assembly.stream.el9, openshift4/ose-pod-rhel9 v4.17.0-202503210032.p0.g98fe569.assembly.stream.el9, openshift4/ose-etcd-rhel9 v4.17.0-202503250204.p0.g0d9e0a9.assembly.stream.el9, openshift4/ose-tests-rhel9 v4.17.0-202503260139.p0.g4a06fd3.assembly.stream.el9, openshift4/ose-tools-rhel9 v4.17.0-202503260139.p0.g0000b3e.assembly.stream.el9, +180 more Red Hat OpenShift Container Platform 4.18 crun 1.20-1.rhaos4.18.el9, perf 5.14.0-427.57.1.el9_4, rtla 5.14.0-427.57.1.el9_4, bpftool 7.3.0-427.57.1.el9_4, kernel 5.14.0-427.57.1.el9_4, butane 0.23.0-1.rhaos4.18.el8, +102 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
23 mo ago

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cri-o/cri-o
<1.29.11
>=1.30.0, <1.30.8
>=1.31.0, <1.31.3
1.29.11
1.30.8
1.31.3

Affected products

  • Red Hat Red Hat OpenShift Container Platform 4.15
  • Red Hat Red Hat OpenShift Container Platform 4.16
  • Red Hat Red Hat OpenShift Container Platform 4.17
  • Red Hat Red Hat OpenShift Container Platform 4.18
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9
  • Red Hat Red Hat OpenShift Container Platform 3.11
  • Red Hat Red Hat OpenShift Container Platform 4

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.