Host file read and write via symlink escape
Published Jun 12, 2024 · Updated Aug 21, 2026
Path traversal in CRI-O 1.28.6, 1.29.4, and 1.30.0 allows attackers to read and write host files through a malicious container image. During container creation, server/container_create_linux.go joined the image-controlled /etc path without securely confining symlink resolution to the container root filesystem. Exploitation requires high-privilege access and deployment of the crafted image, after which container processes can read or overwrite host files.
Summary
What happened
Path traversal in CRI-O 1.28.6, 1.29.4, and 1.30.0 allows attackers to read and write host files through a malicious container image. During container creation, server/container_create_linux.go joined the image-controlled /etc path without securely confining symlink resolution to the container root filesystem. Exploitation requires high-privilege access and deployment of the crafted image, after which container processes can read or overwrite host files.
The record
- CVE
- CVE-2024-5154
- Published
- Jun 12, 2024
- Updated
- Aug 21, 2026
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform 4.14
- Classifications
- CWE-22, T1611
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream malicious-container reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo