Docker vulnerabilities

Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.

Docker version 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted image or build in a Dockerfile in an LZMA (.xz) archive.

Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a symlink or hard link attack in an image archive during a pull or load operation.

Docker version 1.0.0 uses world-readable and world-writable permissions on the management socket, allowing local users to gain privileges via unspecified vectors.

A vulnerability exists in the bind-propagation option of the Dockerfile RUN --mount instruction. The system does not properly validate the input passed to this option, allowing users to pass arbitrary parameters to the mount instruction. This issue can be exploited to mount sensitive directories from the host into a container during the build process and, in some cases, modify the contents of those mounted files. Even if SELinux is used, this vulnerability can bypass its protection by allowing the source directory to be relabeled to give the container access to host files.