Loading vulnerability…
Kata Containers fails to restrict containers from accessing the Kata guest’s root filesystem device. A malicious container can leverage this improper privilege management to access the guest root filesystem device, obtain code execution within the guest, and masquerade as the kata-agent. Affected versions include Kata Containers 1.11 prior to 1.11.1, 1.10 prior to 1.10.5, and 1.9 and earlier.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2020-2023, targeting Kata Containers (kata-runtime 1.11.0) on Linux with KVM support. The exploit demonstrates two main container escape techniques: 1. Overwriting the guest's systemd-shutdown binary via mknod and debugfs, allowing arbitrary code execution during shutdown. The script 'yuvalavra-overwrite-systemd-shutdown-escape-to-guest.sh' automates this process, including creating a proof file in the guest. 2. Overwriting the coredump-wrapper binary with a reverse shell script ('reverse_shell'), then triggering a segmentation fault to execute the shell and connect back to the attacker's host (172.17.0.1:2333). This is automated by 'ssst0n3-core-pattern-escape-to-guest.sh'. The repository includes supporting files such as 'malloc.c' (for memory exhaustion), segmentation fault triggers, and utility scripts. The Dockerfile sets up the required environment. The exploit requires the ability to run privileged containers with kata-runtime and access to debugfs and mknod. The main impact is container escape to guest VM with arbitrary code execution, including the ability to establish a reverse shell.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.