CVE-2024-9407

Improper Input Validation in Buildah and Podman

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-9407 has a CVSS score of 4.7 (Medium). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.37.4, 5.2.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2024-9407? CVE-2024-9407 is a medium-severity improper input validation vulnerability in github.com/containers/buildah (go), affecting versions <= 1.37.3. It is fixed in 1.37.4, 5.2.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2024-9407? CVE-2024-9407 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-9407?
   • github.com/containers/buildah (go) (versions <= 1.37.3)
   • github.com/containers/podman/v5 (go) (versions <= 5.2.3)
   • github.com/containers/podman (go) (versions <= 5.2.3)
   • github.com/containers/podman/v2 (go) (versions <= 5.2.3)
   • github.com/containers/podman/v3 (go) (versions <= 5.2.3)
   • github.com/containers/podman/v4 (go) (versions <= 5.2.3)
4. Is there a fix for CVE-2024-9407? Yes. CVE-2024-9407 is fixed in 1.37.4, 5.2.4. Upgrade to this version or later.
5. Is CVE-2024-9407 exploitable, and should I be worried? Whether CVE-2024-9407 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-9407 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-9407?
   • Upgrade github.com/containers/buildah to 1.37.4 or later
   • Upgrade github.com/containers/podman/v5 to 5.2.4 or later
   • Upgrade github.com/containers/podman to 5.2.4 or later
   • Upgrade github.com/containers/podman/v2 to 5.2.4 or later
   • Upgrade github.com/containers/podman/v3 to 5.2.4 or later
   • Upgrade github.com/containers/podman/v4 to 5.2.4 or later

Other vulnerabilities in github.com/containers/buildah