Container escape through host runc binary overwrite
CVE-2019-5736 is a container escape vulnerability affecting runc through 1.0-rc6, including its use in Docker before 18.09.2. Improper handling of executable file descriptors exposes the host runtime executable to container processes, allowing an attacker executing as root inside a container to overwrite the host runc binary. Exploitation can occur when an attacker-controlled image is started or when a process is executed in an existing container that the attacker has previously modified. Subsequent runtime execution can execute attacker-controlled code as root on the host. Docker containers using default settings are affected; the equivalent LXC flaw affects privileged containers.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation breaks container isolation, permits modification of the host runc executable, and enables arbitrary command execution with host root privileges. This can result in full host compromise. Overwriting the runtime can also break container runtime functionality.
If you can’t patch tonight, do this now.
Avoid untrusted container images and restrict access to container management interfaces, including Docker APIs. Run containers as non-root where possible. User namespace remapping mitigates this attack by mapping container root to an unprivileged host identity that cannot write the host runc executable; unprivileged LXC containers use this isolation by default. These controls do not replace runtime updates. Cisco identifies no product-specific workarounds in its advisory.
Patch, then assume compromise.
Upgrade runc and LXC to vendor-patched releases, and upgrade affected Docker installations to 18.09.2 or later. The runtime fix re-executes from a sealed anonymous in-memory executable copy rather than exposing the writable host binary. Apply relevant product-specific updates. For AWS, replace affected instances or nodes with patched AMIs; use Fargate Platform Version 1.3 or later and redeploy tasks. Update AWS IoT Greengrass to 1.7.1, or the documented 1.6.1 update with Linux kernel 3.17 or greater. Restart applicable SageMaker jobs or notebook instances to apply updates. Documented Cisco fixes include Cisco Container Platform 3.1.0 and Cisco Defense Orchestrator On-prem 19.8; other products require their vendor-specific fixed releases.
9 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.