dbcve.org
Cri OApplication · Kubernetes

CVE-2024-5154

HIGH · 8.1 CVSS v3.1 Published 2024-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in cri-o allows malicious containers to create symbolic links pointing to arbitrary host files through directory traversal using '../' sequences. This enables a container to escape its isolation and read or write to files outside its intended filesystem boundary on the host system.

MitigationUpgrade cri-o to the patched version and consider configuring read-only container filesystems, disabling symlink following, or implementing user namespace isolation to limit container escape paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cri OApplication
Affected:= 1.28.6= 1.29.4= 1.30.0
Openshift Container PlatformApplication
Affected:= 3.11= 4.0= 4.12= 4.13= 4.14= 4.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify cri-o is present
    Run 'crio --version' or check for the crio service with 'systemctl status crio'
    Affected if crio is not installed or not running, the vulnerability does not apply
  2. Check cri-o version
    Run 'crio --version' and note the output version number
    Affected if The version matches exactly 1.28.6, 1.29.4, or 1.30.0
  3. Check OpenShift cluster version (if applicable)
    Run 'oc get clusterversion' or check '/etc/redhat-release' on master nodes
    Affected if The OpenShift version is 3.11, 4.0, 4.12, 4.13, 4.14, or 4.15 and uses cri-o as the container runtime
  4. Confirm container isolation configuration
    Inspect container runtime configuration in /etc/crio/crio.conf or via 'crictl info' for runtime settings related to symlink handling
    Affected if The configuration allows containers to create symlinks that can traverse outside the container filesystem (default behavior in vulnerable versions)

You are affected if you are running cri-o versions 1.28.6, 1.29.4, or 1.30.0, or OpenShift versions 3.11, 4.0, 4.12-4.15 with cri-o as the container runtime.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade cri-o to the patched version and consider configuring read-only container filesystems, disabling symlink following, or implementing user namespace isolation to limit container escape paths.

Recommended fix Moderate confidence

Latest available CRI-O version in each respective release branch (1.28.x, 1.29.x, 1.30.x) with CVE-2024-5154 fixed; OCP 4.12/4.13 to latest available z-stream update

  1. Identify your current CRI-O or OpenShift Container Platform version using 'crio --version' or 'oc get clusterversion'
  2. For CRI-O: Upgrade to the latest available version in your release stream (1.28.x, 1.29.x, or 1.30.x) that includes the security fix
  3. For OpenShift Container Platform: Apply the latest platform update or errata for your specific version (3.11, 4.12, or 4.13) via 'oc adm upgrade' or the Red Hat Hybrid Cloud Console
  4. After upgrade, verify the CRI-O version matches the fixed release using 'crio --version'
  5. Test container runtime functionality to ensure the upgrade did not break existing workloads
Caveat Review release notes for your specific version upgrade; OCP 3.11 is approaching end-of-life and may require broader platform migration planning

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cri O Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5154 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data