LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A person able to access powerful Kubernetes runtime sockets could abuse container checkpoint restoration to reintroduce host mounts that pod rules would reject. This could expose or modify sensitive host data. The issue is serious, but the supplied evidence requires access to the kubelet or CRI-O socket.

Executive priority

Treat this as high priority where runtime sockets are exposed beyond tightly controlled administrators or services; contain that access immediately. Elsewhere, schedule prompt vendor-guided remediation and configuration review. The supplied evidence does not establish an unauthenticated, internet-wide attack path.

Technical view

CRI-O restores mounts from a checkpoint archive rather than the requested pod specification. Consequently, validation of pod-declared mount access does not cover restored mounts, enabling unauthorized host mounts. The supplied CVSS 3.1 score is 7.4, with high confidentiality and integrity impact, high attack complexity, and no stated availability impact.

Likely exposure

Prioritize CRI-O and OpenShift nodes matching vendor-affected builds, especially where tenants, automation, or compromised workloads can reach kubelet or CRI-O sockets. Ordinary pod access alone is not shown sufficient. Because the bundle marks related packages variously affected, unaffected, or unknown, validate exact products, packages, and builds.

Exploitation context

Exploitation requires access to the kubelet or CRI-O socket and invocation of checkpoint restoration. Attack complexity is rated high. The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. KEV absence does not prove exploitation has never occurred.

Researcher notes

The security boundary fails because mount authorization evaluates the pod specification while restoration consumes archive-sourced mount state. Focus assessment on namespace separation, archive provenance, and socket authorization. The affected matrix is heterogeneous and does not provide reliable continuous version ranges; avoid extrapolating beyond the explicitly listed product and build statuses.

Mitigation direction

  • Match deployed builds against Red Hat advisories and follow the applicable vendor remediation guidance.
  • Restrict kubelet and CRI-O socket access to essential administrators and privileged services.
  • Remove unintended runtime-socket mounts or access paths from workloads and automation.
  • Investigate and contain any suspected unauthorized access to runtime control sockets.

Validation and detection

  • Inventory CRI-O, OpenShift, RHCOS, Podman, and conmon packages with their exact builds.
  • Compare each detected build with the affected status in Red Hat guidance.
  • Verify socket permissions, ownership, mounts, and access paths exclude untrusted identities and workloads.
  • Review available audit and service logs for unexpected checkpoint or restore activity.
  • After remediation, confirm updated build status and revalidate runtime-socket restrictions.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-8676 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2024-8676Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineredhat

    Reported to Red Hat.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorcri-ocri-o, 0, 1.30.0, 1.31.0unaffected
Red HatRed Hat OpenShift Container Platform 4.15cri-o, 0:1.28.11-7.rhaos4.15.gitc4c0556.el8affected
Red HatRed Hat OpenShift Container Platform 4.16cri-o, 0:1.29.11-3.rhaos4.16.git16d9bd6.el8affected
Red HatRed Hat OpenShift Container Platform 4.16rhcos, 416.94.202506251808-0affected
Red HatRed Hat OpenShift Container Platform 4.17rhcos, 417.94.202503241418-0affected
Red HatRed Hat OpenShift Container Platform 4.18cri-o, 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8affected
Red HatRed Hat OpenShift Container Platform 4.18rhcos, 418.94.202504231329-0affected
Red HatRed Hat Enterprise Linux 8container-tools:rhel8/conmonunaffected
Red HatRed Hat Enterprise Linux 8container-tools:rhel8/podmanaffected
Red HatRed Hat Enterprise Linux 9conmonaffected
Red HatRed Hat OpenShift Container Platform 3.11cri-ounknown
Red HatRed Hat OpenShift Container Platform 4conmonunaffected
Red HatRed Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9affected
Weakness

CWE details

CWE-285

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs