Vulnerabilities (CVE)

Filtered by vendor Docker Subscribe
Filtered by product Docker
Total 53 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2021-20511 2 Docker, Ibm 2 Docker, Security Verify Access 2021-09-29 6.8 MEDIUM 4.9 MEDIUM
IBM Security Verify Access Docker 10.0.0 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 198300.
CVE-2021-20497 2 Docker, Ibm 2 Docker, Security Verify Access 2021-09-29 5.0 MEDIUM 7.5 HIGH
IBM Security Verify Access Docker 10.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 197969
CVE-2021-20496 2 Docker, Ibm 2 Docker, Security Verify Access 2021-09-29 4.0 MEDIUM 4.9 MEDIUM
IBM Security Verify Access Docker 10.0.0 could allow an authenticated user to bypass input due to improper input validation. IBM X-Force ID: 197966.
CVE-2020-27534 1 Docker 1 Docker 2021-01-05 5.0 MEDIUM 5.3 MEDIUM
util/binfmt_misc/check.go in Builder in Docker Engine before 19.03.9 calls os.OpenFile with a potentially unsafe qemu-check temporary pathname, constructed with an empty first argument in an ioutil.TempDir call.
CVE-2016-3697 3 Docker, Linuxfoundation, Opensuse 3 Docker, Runc, Opensuse 2021-01-05 2.1 LOW 7.8 HIGH
libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.
CVE-2019-13139 1 Docker 1 Docker 2020-08-24 4.6 MEDIUM 8.4 HIGH
In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the "docker build" command would be able to gain command execution. An issue exists in the way "docker build" processes remote git URLs, and results in command injection into the underlying "git clone" command, leading to code execution in the context of the user executing the "docker build" command. This occurs because git ref can be misinterpreted as a flag.
CVE-2014-9356 1 Docker 1 Docker 2019-12-11 8.5 HIGH 8.6 HIGH
Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a container protection mechanism via a full pathname in a symlink in an (1) image or (2) build in a Dockerfile.
CVE-2018-15664 1 Docker 1 Docker 2019-06-25 6.2 MEDIUM 7.5 HIGH
In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker cp' command are vulnerable to a symlink-exchange attack with Directory Traversal, giving attackers arbitrary read-write access to the host filesystem with root privileges, because daemon/archive.go does not do archive operations on a frozen filesystem (or from within a chroot).
CVE-2018-15514 1 Docker 1 Docker 2018-11-09 6.5 MEDIUM 8.8 HIGH
HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over the \\.\pipe\dockerBackend named pipe without verifying the validity of the deserialized .NET objects. This would allow a malicious user in the "docker-users" group (who may not otherwise have administrator access) to escalate to administrator privileges.
CVE-2014-0047 1 Docker 1 Docker 2017-10-13 4.6 MEDIUM 7.8 HIGH
Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage.
CVE-2016-8867 1 Docker 1 Docker 2017-07-28 5.0 MEDIUM 7.5 HIGH
Docker Engine 1.12.2 enabled ambient capabilities with misconfigured capability policies. This allowed malicious images to bypass user permissions to access files within the container filesystem or mounted volumes.
CVE-2014-6408 1 Docker 1 Docker 2014-12-15 5.0 MEDIUM N/A
Docker 1.3.0 through 1.3.1 allows remote attackers to modify the default run profile of image containers and possibly bypass the container by applying unspecified security options to an image.
CVE-2014-6407 1 Docker 1 Docker 2014-12-15 7.5 HIGH N/A
Docker before 1.3.2 allows remote attackers to write to arbitrary files and execute arbitrary code via a (1) symlink or (2) hard link attack in an image archive in a (a) pull or (b) load operation.