Moby: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap
moby
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/docker Go |
| No fix yet |
| github.com/moby/moby/v2 Go |
|
|
| github.com/moby/moby Go |
moby
| Product | Affected | Fixed in |
|---|---|---|
| github.com/docker/docker Go |
| No fix yet |
| github.com/moby/moby/v2 Go |
|
|
| github.com/moby/moby Go |
|
| No fix yet |
Moby is an open source container framework. In Docker Engine prior to version 29.5.1, Docker Daemon versions 28.5.2 and prior, and Moby Daemon prior to version 2.0.0-beta.14, a race condition during docker cp mount setup allows a malicious container to create empty files or directories at arbitrary absolute paths on the host filesystem. This issue has been patched in Docker Engine version 29.5.1 and Moby Daemon version 2.0.0-beta.14.
From the CVE record · GitHub_M
A race condition during docker cp mount setup affects Docker Engine before 29.5.1, Docker Daemon 28.5.2 and earlier, and Moby Daemon before 2.0.0-beta.14. When docker cp sets up a mount, a malicious container can create empty files or directories at arbitrary absolute paths on the host filesystem.
Teams running those Docker Engine, Docker Daemon, or Moby Daemon versions, or using the affected Go packages github.com/docker/docker, github.com/moby/moby, or github.com/moby/moby/v2, should check their deployments.