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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
|
Configuration 7 (hide)
|
Configuration 8 (hide)
|
Configuration 9 (hide)
|
Configuration 10 (hide)
|
Configuration 11 (hide)
|
Configuration 12 (hide)
|
Configuration 13 (hide)
|
Information
Published : 2019-02-11 11:29
Updated : 2021-12-16 10:38
NVD link : CVE-2019-5736
Mitre link : CVE-2019-5736
JSON object : View
CWE
CWE-78
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Products Affected
linuxcontainers
- lxc
linuxfoundation
- runc
- kubernetes_engine
apache
- mesos
docker
- docker
redhat
- enterprise_linux
- container_development_kit
- openshift
- enterprise_linux_server
hp
- onesphere
opensuse
- backports_sle
- leap
d2iq
- dc\/os
- kubernetes_engine
netapp
- solidfire
- hci_management_node
fedoraproject
- fedora
canonical
- ubuntu_linux
microfocus
- service_management_automation