First published: Mon Sep 30 2019(Updated: )
runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory. References: <a href="https://github.com/opencontainers/runc/issues/2128">https://github.com/opencontainers/runc/issues/2128</a>
Affected Software | Affected Version | How to fix |
---|---|---|
OpenContainers runc | >=1.0.0-rc8<=1.0.0-rc8 | |
Docker | <=19.03.2-ce |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1757214 is typically considered high due to the potential for AppArmor restriction bypass.
To fix REDHAT-BUG-1757214, update runc to a version later than 1.0.0-rc8 and Docker to a version beyond 19.03.2-ce.
The vulnerability REDHAT-BUG-1757214 affects OpenContainers runc versions up to 1.0.0-rc8 and Docker versions up to 19.03.2-ce.
Yes, REDHAT-BUG-1757214 can impact production systems using the affected versions of runc and Docker if exploited.
An attacker could leverage REDHAT-BUG-1757214 to bypass AppArmor restrictions and potentially gain unauthorized access to the host system through the Docker container.