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.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "docker-doc": "18.06.1-0ubuntu1.2~16.04.1", "docker.io": "18.06.1-0ubuntu1.2~16.04.1", "golang-github-docker-docker-dev": "18.06.1-0ubuntu1.2~16.04.1", "golang-docker-dev": "18.06.1-0ubuntu1.2~16.04.1", "vim-syntax-docker": "18.06.1-0ubuntu1.2~16.04.1" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "runc": "1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1", "runc-dbgsym": "1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1", "golang-github-opencontainers-runc-dev": "1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "docker-doc": "18.06.1-0ubuntu1.2~18.04.1", "docker.io": "18.06.1-0ubuntu1.2~18.04.1", "golang-github-docker-docker-dev": "18.06.1-0ubuntu1.2~18.04.1", "golang-docker-dev": "18.06.1-0ubuntu1.2~18.04.1", "vim-syntax-docker": "18.06.1-0ubuntu1.2~18.04.1" } ] }