Container escape via symlinked bind-mount source
Published Mar 18, 2024 · Updated Mar 4, 2026
Improper link resolution in Buildah and Podman Build allows context-dependent attackers to escape a build container via a malicious Containerfile. GetBindMount in internal/volumes/volumes.go cleans and joins an attacker-controlled mount source without resolving symlinks beneath the build context. A victim must run the crafted build locally; SELinux enforcement limits the escape to host-file reads, while disabling it permits host-file writes.
Summary
What happened
Improper link resolution in Buildah and Podman Build allows context-dependent attackers to escape a build container via a malicious Containerfile. GetBindMount in internal/volumes/volumes.go cleans and joins an attacker-controlled mount source without resolving symlinks beneath the build context. A victim must run the crafted build locally; SELinux enforcement limits the escape to host-file reads, while disabling it permits host-file writes.
The record
- CVE
- CVE-2024-1753
- Published
- Mar 18, 2024
- Updated
- Mar 4, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-59, T1611
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- Mar 4, 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
- Buildah malicious Containerfile reproducerproof 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