Docker Desktop

Docker Desktop before 4.12.0 is vulnerable to RCE via a crafted extension description or changelog

Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route

Docker Desktop before 4.23.0 allows Enhanced Container Isolation bypass via debug shell

Docker Model Runner container-to-host code execution via MLX-LM model_file importlib loading

Docker Model Runner container-to-host code execution via unsandboxed trust_remote_code in Python inference backends

Docker Desktop Enhanced Container Isolation bypass via --use-api-socket CLI flag

Docker Desktop 4.3.0 has Incorrect Access Control.

Docker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL

An issue was discovered in Docker Desktop through 2.2.0.5 on Windows. If a local attacker sets up their own named pipe prior to starting Docker with the same name, this attacker can intercept a connection attempt from Docker Service (which runs as SYSTEM), and then impersonate their privileges.

com.docker.vmnetd in Docker Desktop 2.3.0.3 allows privilege escalation because of a lack of client verification.

In Docker Desktop on Windows before 4.12.0 an argument injection to installer may result in LPE

Docker Desktop before 4.17.0 allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious docker-desktop:// URL

Docker Desktop 4.11.x allows --no-windows-containers flag bypass

Expired Personal Access Tokens (PATs) are recorded in Docker Desktop diagnostic logs

Docker Desktop installer on Windows in versions before 4.6.0 allows an attacker to overwrite any administrator writable files by creating a symlink in place of where the installer writes its log file. Starting from version 4.6.0, the Docker Desktop installer, when run elevated, will write its log files to a location not writable by non-administrator users.

Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation restrictions via the raw Docker socket and launch privileged containers

Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files.

Docker Desktop before 4.4.4 on Windows allows attackers to move arbitrary files.