Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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

Noroxi assessment

Priority: Monitor (action score 29/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.75% (FIRST EPSS); higher than 54.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: github.com/cri-o/cri-o cri-o 1.29.11, 1.30.8, 1.31.3.

Low priority for now. Upgrade to github.com/cri-o/cri-o cri-o 1.29.11, 1.30.8, 1.31.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.4 · v3.1—No exploit Fix available
Published
Nov 26, 2024
Updated
Oct 13, 2026
EPSS
0.7% · 54th percentile

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
29 / 40 · 7.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
7.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-8676

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for red hat records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • github.com/cri-o/cri-o cri-o

    • before 1.29.11affected · semver
    • 1.30.0 and later · before 1.30.8affected · semver
    • 1.31.0 and later · before 1.31.3affected · semver

  • Red Hat Red Hat Enterprise Linux 8

    • all versionsunknown
    • all versionsaffected

  • Red Hat Red Hat Enterprise Linux 9

    • all versionsaffected

  • Red Hat Red Hat OpenShift Container Platform 3.11

    • all versionsunknown

  • Red Hat Red Hat OpenShift Container Platform 4

    • all versionsunknown

  • Red Hat Red Hat OpenShift Container Platform 4.15

    • 0:1.28.11-7.rhaos4.15.gitc4c0556.el8 and laternot affected · rpm

  • Red Hat Red Hat OpenShift Container Platform 4.16

    • 0:1.29.11-3.rhaos4.16.git16d9bd6.el8 and laternot affected · rpm
    • 416.94.202506251808-0 and laternot affected · rpm

  • Red Hat Red Hat OpenShift Container Platform 4.17

    • 417.94.202503241418-0 and laternot affected · rpm

  • Red Hat Red Hat OpenShift Container Platform 4.18

    • 0:1.31.5-5.rhaos4.18.git6dfa0a6.el8 and laternot affected · rpm
    • 418.94.202504231329-0 and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/cri-o/cri-ofrom 1.30.0 · before 1.30.81.30.8
Gogithub.com/cri-o/cri-ofrom 1.31.0 · before 1.31.31.31.3
Gogithub.com/cri-o/cri-obefore 1.29.111.29.11
Red Hat:openshift:4.15::el8cri-obefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el80:1.28.11-7.rhaos4.15.gitc4c0556.el8
Red Hat:openshift:4.15::el8cri-o-debuginfobefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el80:1.28.11-7.rhaos4.15.gitc4c0556.el8
Red Hat:openshift:4.15::el8cri-o-debugsourcebefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el80:1.28.11-7.rhaos4.15.gitc4c0556.el8
Red Hat:openshift:4.15::el9cri-obefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el90:1.28.11-7.rhaos4.15.gitc4c0556.el9
Red Hat:openshift:4.15::el9cri-o-debuginfobefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el90:1.28.11-7.rhaos4.15.gitc4c0556.el9
Red Hat:openshift:4.15::el9cri-o-debugsourcebefore 0:1.28.11-7.rhaos4.15.gitc4c0556.el90:1.28.11-7.rhaos4.15.gitc4c0556.el9
Red Hat:openshift:4.16::el8cri-obefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el80:1.29.11-3.rhaos4.16.git16d9bd6.el8
Red Hat:openshift:4.16::el8cri-o-debuginfobefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el80:1.29.11-3.rhaos4.16.git16d9bd6.el8
Red Hat:openshift:4.16::el8cri-o-debugsourcebefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el80:1.29.11-3.rhaos4.16.git16d9bd6.el8
Red Hat:openshift:4.16::el9cri-obefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el90:1.29.11-3.rhaos4.16.git16d9bd6.el9
Red Hat:openshift:4.16::el9cri-o-debuginfobefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el90:1.29.11-3.rhaos4.16.git16d9bd6.el9
Red Hat:openshift:4.16::el9cri-o-debugsourcebefore 0:1.29.11-3.rhaos4.16.git16d9bd6.el90:1.29.11-3.rhaos4.16.git16d9bd6.el9
Red Hat:openshift:4.18::el8cri-obefore 0:1.31.5-5.rhaos4.18.git6dfa0a6.el80:1.31.5-5.rhaos4.18.git6dfa0a6.el8
Red Hat:openshift:4.18::el8cri-o-debuginfobefore 0:1.31.5-5.rhaos4.18.git6dfa0a6.el80:1.31.5-5.rhaos4.18.git6dfa0a6.el8
Red Hat:openshift:4.18::el8cri-o-debugsourcebefore 0:1.31.5-5.rhaos4.18.git6dfa0a6.el80:1.31.5-5.rhaos4.18.git6dfa0a6.el8
Red Hat:openshift:4.18::el9buildahbefore 2:1.33.12-1.rhaos4.18.el92:1.33.12-1.rhaos4.18.el9
Red Hat:openshift:4.18::el9buildah-debuginfobefore 2:1.33.12-1.rhaos4.18.el92:1.33.12-1.rhaos4.18.el9
Red Hat:openshift:4.18::el9buildah-debugsourcebefore 2:1.33.12-1.rhaos4.18.el92:1.33.12-1.rhaos4.18.el9
Red Hat:openshift:4.18::el9buildah-testsbefore 2:1.33.12-1.rhaos4.18.el92:1.33.12-1.rhaos4.18.el9
Red Hat:openshift:4.18::el9buildah-tests-debuginfobefore 2:1.33.12-1.rhaos4.18.el92:1.33.12-1.rhaos4.18.el9
Red Hat:openshift:4.18::el9cri-obefore 0:1.31.5-5.rhaos4.18.git6dfa0a6.el90:1.31.5-5.rhaos4.18.git6dfa0a6.el9

+2

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
github.com/cri-o/cri-o cri-o1.29.11Vendor (CNA)
github.com/cri-o/cri-o cri-o1.30.8Vendor (CNA)
github.com/cri-o/cri-o cri-o1.31.3Vendor (CNA)
Go:github.com/cri-o/cri-o1.29.11Package registry (OSV)
Go:github.com/cri-o/cri-o1.30.8Package registry (OSV)
Go:github.com/cri-o/cri-o1.31.3Package registry (OSV)
red hat:buildah2:1.33.12-1.rhaos4.18.el9 · Red Hat:openshift:4.18::el9Package registry (OSV)
red hat:buildah-debuginfo2:1.33.12-1.rhaos4.18.el9 · Red Hat:openshift:4.18::el9Package registry (OSV)
red hat:buildah-debugsource2:1.33.12-1.rhaos4.18.el9 · Red Hat:openshift:4.18::el9Package registry (OSV)
red hat:buildah-tests2:1.33.12-1.rhaos4.18.el9 · Red Hat:openshift:4.18::el9Package registry (OSV)
red hat:buildah-tests-debuginfo2:1.33.12-1.rhaos4.18.el9 · Red Hat:openshift:4.18::el9Package registry (OSV)
red hat:cri-o0:1.29.11-3.rhaos4.16.git16d9bd6.el8 · Red Hat:openshift:4.16::el8Package registry (OSV)
red hat:cri-o-debuginfo0:1.29.11-3.rhaos4.16.git16d9bd6.el8 · Red Hat:openshift:4.16::el8Package registry (OSV)
red hat:cri-o-debugsource0:1.29.11-3.rhaos4.16.git16d9bd6.el8 · Red Hat:openshift:4.16::el8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-285 · Improper Authorization

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records