NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2024-11218: Buildah allows build breakout using malicious Containerfiles and concurrent builds

highCVSS 3.1 8.6GHSA-5vpc-35f4-r8w6

Impact With careful use of the --mount flag in RUN instructions in Containerfiles, and by using either multi-stage builds with use of concurrently-executing build stages (e.g., using the --jobs CLI flag) or multiple separate but concurrently-executing builds, a malicious Containerfile can be used to expose content from the build host to the command being run using the RUN instruction.

Published Jan 21, 2025 · Updated Oct 2, 2025

Affected packages

github.com/containers/buildah

Ecosystem
Go
Affected
>= 1.38.0, < 1.38.1
Fixed in
1.38.1
Check
go list -m github.com/containers/buildah

github.com/containers/buildah

Ecosystem
Go
Affected
>= 1.37.0, < 1.37.6
Fixed in
1.37.6
Check
go list -m github.com/containers/buildah

github.com/containers/buildah

Ecosystem
Go
Affected
>= 1.35.0, < 1.35.5
Fixed in
1.35.5
Check
go list -m github.com/containers/buildah

github.com/containers/buildah

Ecosystem
Go
Affected
< 1.33.12
Fixed in
1.33.12
Check
go list -m github.com/containers/buildah

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

With careful use of the --mount flag in RUN instructions in Containerfiles, and by using either multi-stage builds with use of concurrently-executing build stages (e.g., using the --jobs CLI flag) or multiple separate but concurrently-executing builds, a malicious Containerfile can be used to expose content from the build host to the command being run using the RUN instruction. This can be used to read or write contents using the privileges of the process which is performing the build. When that process is a root-owned podman system service which is provided for use by unprivileged users, this includes the ability to read and write contents which the client should not be allowed to read and write, including setuid executables in locations where they can be later accessed by unprivileged users.

Patches

Patches have been merged to the main branch, and will be added to upcoming releases on the release-1.38, release-1.37, release-1.35, and release-1.33 branches.

This addressed a number of Jira cards, but primarily https://issues.redhat.com/browse/RHEL-67616 and https://issues.redhat.com/browse/RHEL-67618, which were then vendored into Podman and backported into olde rbranches.

Workarounds

Mandatory access controls should limit the access of the process performing the build, on systems where they are enabled.

Credited to eriksjolund.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries