Docker Desktop Docker Plugins Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
Docker CLI · Docker Compose
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/cli Go |
|
|
| github.com/docker/compose Go |
| No fix yet |
Docker CLI · Docker Compose
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/cli Go |
|
|
| github.com/docker/compose Go |
| No fix yet |
| github.com/docker/compose/v2 Go |
|
| No fix yet |
| github.com/docker/compose/v5 Go |
|
|
Docker CLI for Windows searches for plugin binaries in C:\ProgramData\Docker\cli-plugins, a directory that does not exist by default. A low-privileged attacker can create this directory and place malicious CLI plugin binaries (docker-compose.exe, docker-buildx.exe, etc.) that are executed when a victim user opens Docker Desktop or invokes Docker CLI plugin features, and allow privilege-escalation if the docker CLI is executed as a privileged user.
This issue affects Docker CLI: through 29.1.5 and Windows binaries acting as a CLI-plugin manager using the github.com/docker/cli/cli-plugins/manager https://pkg.go.dev/github.com/docker/cli@v29.1.5+incompatible/cli-plugins/manager package, such as Docker Compose.
This issue does not impact non-Windows binaries, and projects not using the plugin-manager code.
From the CVE record · Docker
On Windows, Docker CLI and binaries using its CLI plugin manager search a directory that does not exist by default. A low-privileged local attacker can create it and place malicious plugins that run when a victim opens Docker Desktop or invokes a CLI plugin feature; privilege escalation is possible if the victim runs Docker CLI as a privileged user. Non-Windows binaries and projects that do not use the plugin manager are not affected.
Check Windows users of Docker CLI through 29.1.5 and binaries using its CLI plugin manager, including affected github.com/docker/compose, github.com/docker/compose/v2 from 2.31.0, and github.com/docker/compose/v5 before 5.1.0.