CVE-2024-11218: Buildah allows build breakout using malicious Containerfiles and concurrent builds
(updated )
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.
References
- access.redhat.com/security/cve/CVE-2024-11218
- bugzilla.redhat.com/show_bug.cgi?id=2326231
- github.com/advisories/GHSA-5vpc-35f4-r8w6
- github.com/containers/buildah
- github.com/containers/buildah/security/advisories/GHSA-5vpc-35f4-r8w6
- issues.redhat.com/browse/RHEL-67616
- issues.redhat.com/browse/RHEL-67618
- nvd.nist.gov/vuln/detail/CVE-2024-11218
Detect and mitigate CVE-2024-11218 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →