Buildah: podman: improper input validation in bind-propagation option of dockerfile run --mount instruction
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.4, 1.37.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A vulnerability exists in the bind-propagation option of the Dockerfile RUN --mount instruction. The system does not properly validate the input passed to this option, allowing users to pass arbitrary parameters to the mount instruction. This issue can be exploited to mount sensitive directories from the host into a container during the build process and, in some cases, modify the contents of those mounted files. Even if SELinux is used, this vulnerability can bypass its protection by allowing the source directory to be relabeled to give the container access to host files.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- podman
fixed in 5.2.4
- buildah
fixed in 1.37.4
- container-tools:rhel8
Version range not reported
- podman
Version range not reported
- buildah
Version range not reported
- buildah
Version range not reported
- openshift/ose-rhel-coreos-9
Version range not reported
- buildah
Version range not reported
- podman
Version range not reported
- buildah
Version range not reported
- openshift4/ose-docker-builder
Version range not reported
- github.com/containers/buildahGo
fixed in 1.37.4
- github.com/containers/podman/v5Go
fixed in 5.2.4
- github.com/containers/podmanGo
fixed in 5.2.4
- github.com/containers/podman/v2Go
fixed in 5.2.4
- github.com/containers/podman/v3Go
fixed in 5.2.4
- github.com/containers/podman/v4Go
fixed in 5.2.4
- github.com/containers/podmanGo
All versions
- github.com/containers/podman/v2Go
All versions
- github.com/containers/podman/v3Go
All versions
- github.com/containers/podman/v4Go
All versions