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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NDocker Desktop
APPDocker4.13.0 – 4.17.0 (bez)
Related vulnerabilities
The Docker CLI --use-api-socket flag bypasses Enhanced Container Isolation (ECI) restrictions in Docker Deskto...
The MLX inference backend in Docker Model Runner on macOS uses the MLX-LM library, which unconditionally impor...
The vllm-metal inference backend in Docker Model Runner on macOS unconditionally sets trust_remote_code=True w...
Docker Desktop before 4.23.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrict...
Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route. This issue affec...