CVE-2019-5736

published 11 Feb 2019 · updated 4 Aug 2024

runc through 1.0-rc6 as used in Docker before 18.09.2 and other products allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image or (2) an existing container to which the attacker previously had write access that can be attached with docker exec. This occurs because of file-descriptor mishandling related to /proc/self/exe.

10.0CriticalCVSS 8.6EPSS 98%4 public exploits

4 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 98%. No fixed version is recorded.

runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.

Exploit evidence

4 public sources

Timeline

Every event on this vulnerability

Severity changedCVE-2019-5736·
10.0Critical

Embed

A live severity badge for an advisory, README or ticket

CVE-2019-5736 severity on Zeptric[![CVE-2019-5736](https://zeptric.io/badge/cve/CVE-2019-5736.svg)](https://zeptric.io/cve/CVE-2019-5736)