Loading vulnerability…
CVE-2024-9676 is a symlink traversal vulnerability in the containers/storage library used by Podman, Buildah, and CRI-O. When processing a container image under an automatically assigned user namespace, the library reads the container's account database file without adequately verifying that it is not a symbolic link. A malicious image can therefore redirect the read operation to an arbitrary host file, causing affected container tooling to hang and consume memory until it is terminated by an out-of-memory condition.
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.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A symlink traversal vulnerability in the containers/storage library affecting Podman, Buildah, and CRI-O that can cause denial of service via OOM kill and allow reading an arbitrary file on the host when processing a malicious image with automatically assigned user namespaces.
A CVE referenced by the erratum; no technical details are provided in this content.
A symlink-traversal vulnerability in the containers/storage library that can cause denial of service in Podman, Buildah, and CRI-O.
A symlink-traversal vulnerability in the containers/storage library that can cause denial of service in Podman, Buildah, and CRI-O.
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.