CVE-2014-3499
HighSummary
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.
Risk Assessment
Local users may exploit this vulnerability to gain unauthorized access to the system, potentially leading to serious security breaches.
Recommendation
It is recommended to update Docker to a newer version that addresses the management socket permission issues.
Other vulnerabilities in Docker 1.0.0
See all- CVE-2014-0047High
Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.
- CVE-2014-9357High
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.
- CVE-2014-6407High
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.
- CVE-2026-66384MediumActively exploited
An authenticated user may write data outside the intended Docker cache path under specific remote-repository conditions.
- CVE-2024-9407Medium
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.
Original NVD description (English source)
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS