GHSA-5vpc-35f4-r8w6 Buildah allows build breakout using malicious Containerfiles and concurrent builds

• Go github.com/containers/buildah: >= 1.38.0, < 1.38.1 → fixed in 1.38.1 • Go github.com/containers/buildah: >= 1.37.0, < 1.37.6 → fixed in 1.37.6 • Go github.com/containers/buildah: >= 1.35.0, < 1.35.5 → fixed in 1.35.5 • Go github.com/containers/buildah: < 1.33.12 → fixed in 1.33.12

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.