First published: Mon Mar 13 2023(Updated: )
Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers without the additional hardening features provided by ECI. This would not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket). The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges. This issue has been fixed in Docker Desktop 4.17.0. Affected Docker Desktop versions: from 4.13.0 before 4.17.0.
Credit: security@docker.com
Affected Software | Affected Version | How to fix |
---|---|---|
Docker Desktop | >=4.13.0<4.17.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Docker Desktop vulnerability is CVE-2023-0629.
The severity level of CVE-2023-0629 is high (7.1).
An unprivileged user can bypass Enhanced Container Isolation (ECI) restrictions in Docker Desktop by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers.
No, Docker Desktop version 4.17.0 is not affected by this vulnerability.
You can find more information about this vulnerability at the following reference: https://docs.docker.com/desktop/release-notes/#4170