CVE-2024-11218: Podman: buildah: container breakout by using --jobs=2 and a race condition when building a malicious containerfile
A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.
Security readout for executives and security teams
Plain-English summary
CVE-2024-11218 is a high-severity Podman/Buildah build flaw. If a system builds a malicious Containerfile with affected tooling, a race condition can allow escape from the build container to the host. SELinux may reduce impact, but the source says host file and directory enumeration can still occur.
Executive priority
Treat this as a priority patching and build-pipeline control issue, especially for CI or shared build infrastructure. The business risk is host compromise from malicious container build input, not broad unauthenticated remote exploitation based on the provided evidence.
Technical view
The issue affects podman build and buildah when building a malicious Containerfile using parallel build jobs. The CVSS 3.1 score is 8.6, with local attack vector, required user interaction, changed scope, and high confidentiality, integrity, and availability impact. Affected Red Hat packages include podman, buildah, container-tools:rhel8, and rhcos across listed RHEL and OpenShift streams.
Likely exposure
Highest exposure is on RHEL or OpenShift build hosts, CI runners, developer workstations, or automation that builds Containerfiles from untrusted users, repositories, pull requests, or third parties using affected Podman or Buildah packages.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Exploitation requires a malicious Containerfile to be built with vulnerable tooling and user interaction. This is most relevant where untrusted build definitions can reach privileged or sensitive host build environments.
Researcher notes
Evidence supports a race condition tied to Podman/Buildah parallel builds and malicious Containerfiles. SELinux may mitigate breakout impact but still permits host enumeration. The bundle lists affected Red Hat products and advisories, but does not provide exploit telemetry or full fixed-version details.
Mitigation direction
Apply the relevant Red Hat security advisories for affected RHEL and OpenShift packages.
Check vendor guidance for fixed package versions before relying on local assumptions.
Avoid building untrusted Containerfiles on affected Podman or Buildah versions.
Restrict who can submit or trigger container builds in CI and shared environments.
Keep SELinux enforcing, but do not treat it as a complete mitigation.
Validation and detection
Inventory Podman, Buildah, container-tools, and RHCOS versions against listed affected packages.
Identify CI runners and developer systems that build external or user-submitted Containerfiles.
Confirm relevant Red Hat advisories have been applied to affected platforms.
Review build pipelines for parallel build usage and untrusted Containerfile inputs.
Verify SELinux enforcement and least-privilege controls on build hosts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
33Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.