CVE-2024-9407 — buildah
MEDIUMCVE-2024-9407 is a medium-severity (CVSS 4.7) Improper Input Validation vulnerability in github.com/containers/buildah. A fix is available for github.com/containers/buildah — see the affected versions and patch details below.
Buildah: podman: improper input validation in bind-propagation option of dockerfile run --mount instruction
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-9407.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-9407 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/containers/buildah🐹github.com/containers/podman/v5🐹github.com/containers/podman🐹github.com/containers/podman/v2🐹github.com/containers/podman/v3🐹github.com/containers/podman/v4Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/containers/buildah | all versions | 1.37.4go get github.com/containers/buildah@v1.37.4 |
| 🐹Go | github.com/containers/podman/v5 | all versions | 5.2.4go get github.com/containers/podman/v5@v5.2.4 |
| 🐹Go | github.com/containers/podman | all versions | 5.2.4go get github.com/containers/podman@v5.2.4 |
| 🐹Go | github.com/containers/podman/v2 | all versions | 5.2.4go get github.com/containers/podman/v2@v5.2.4 |
| 🐹Go | github.com/containers/podman/v3 | all versions | 5.2.4go get github.com/containers/podman/v3@v5.2.4 |
| 🐹Go | github.com/containers/podman/v4 | all versions | 5.2.4go get github.com/containers/podman/v4@v5.2.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/buildah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/buildah to 1.37.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9407 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-9407 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-9407. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is classified as moderate rather than important because it requires the attacker to have build privileges on the system, which inherently limits the scope of exploitation to trusted or semi-trusted users who already have some level of access. Additionally, while the flaw allows mounting and…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:rhel8-8100020241023085649.afee755d | RHSA-2024:8846 |
| Red Hat Enterprise Linux 9 | podman-4:4.9.4-16.el9_4 | RHSA-2024:9051 |
| Red Hat Enterprise Linux 9 | podman-4:5.2.2-9.el9_5 | RHSA-2024:9454 |
| Red Hat Enterprise Linux 9 | buildah-2:1.37.5-1.el9_5 | RHSA-2024:9459 |
| Red Hat Enterprise Linux 9.4 Extended Update Support | buildah-2:1.33.11-1.el9_4 | RHSA-2024:9926 |
| Red Hat OpenShift Container Platform 4.16 | rhcos-416.94.202411201433-0 | RHSA-2024:10147 |
Frequently Asked Questions
Is CVE-2024-9407 in your dependencies?
O3 Security finds CVE-2024-9407 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.