Loading vulnerability…
CVE-2024-11218 is a race condition in Podman and Buildah container-image builds. A malicious Containerfile can exploit concurrent build execution with the --jobs=2 option, including use of RUN mount functionality, to break isolation between the build environment and its host. The flaw can expose host filesystem content to the build process and, depending on the privileges of the process conducting the build, can permit host-content modification.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the updated Red Hat OpenShift Dev Spaces 3 container images; the advisory provides no technical details.
A container-breakout vulnerability in Podman and Buildah involving the --jobs=2 option and a race condition while building a malicious Containerfile.
A Buildah/Podman container-breakout vulnerability involving --jobs=2 and a race condition while building a malicious Containerfile.
A CVE included in the advisory's CVE list; no vulnerability details are provided in the content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.