Search for packages
| purl | pkg:deb/ubuntu/docker.io@0.6.7%2Bdfsg1-2 |
| Next non-vulnerable version | 20.10.7-0ubuntu5~20.04.2 |
| Latest non-vulnerable version | 20.10.7-0ubuntu5~20.04.2 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1a7v-a4dt-aaam
Aliases: CVE-2018-15664 |
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). |
Affected by 8 other vulnerabilities. |
|
VCID-1ws7-n691-aaap
Aliases: CVE-2017-14992 GHSA-hqwh-8xv9-42hw |
Lack of content verification in Docker-CE (Also known as Moby) versions 1.12.6-0, 1.10.3, 17.03.0, 17.03.1, 17.03.2, 17.06.0, 17.06.1, 17.06.2, 17.09.0, and earlier allows a remote attacker to cause a Denial of Service via a crafted image layer payload, aka gzip bombing. |
Affected by 11 other vulnerabilities. |
|
VCID-7e47-wjej-aaaf
Aliases: CVE-2014-8178 |
Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 do not use a globally unique identifier to store image layers, which makes it easier for attackers to poison the image cache via a crafted image in pull or push commands. |
Affected by 16 other vulnerabilities. |
|
VCID-93wz-5xtd-aaae
Aliases: CVE-2014-0047 |
Docker before 1.5 allows local users to have unspecified impact via vectors involving unsafe /tmp usage. |
Affected by 19 other vulnerabilities. Affected by 20 other vulnerabilities. |
|
VCID-98m9-ft46-aaah
Aliases: CVE-2021-41089 GHSA-v994-f8vw-g7j4 |
Moby is an open-source project created by Docker to enable software containerization. A bug was found in Moby (Docker Engine) where attempting to copy files using `docker cp` into a specially-crafted container can result in Unix file permission changes for existing files in the host’s filesystem, widening access to others. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in Moby (Docker Engine) 20.10.9. Users should update to this version as soon as possible. Running containers do not need to be restarted. |
Affected by 1 other vulnerability. |
|
VCID-9ena-9ujd-aaaa
Aliases: CVE-2015-3631 GHSA-v4h8-794j-g8mm |
Docker Engine before 1.6.1 allows local users to set arbitrary Linux Security Modules (LSM) and docker_t policies via an image that allows volumes to override files in /proc. |
Affected by 19 other vulnerabilities. Affected by 20 other vulnerabilities. |
|
VCID-aqg7-3kp1-aaaf
Aliases: CVE-2014-6407 GHSA-5qgp-p5jc-w2rm |
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. |
Affected by 19 other vulnerabilities. |
|
VCID-cgzb-3tqk-aaaj
Aliases: CVE-2015-3629 GHSA-g44j-7vp3-68cv |
Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container. |
Affected by 19 other vulnerabilities. Affected by 20 other vulnerabilities. |
|
VCID-cvtk-d332-aaaf
Aliases: CVE-2021-21285 GHSA-6fj5-m822-rqx8 |
In Docker before versions 9.03.15, 20.10.3 there is a vulnerability in which pulling an intentionally malformed Docker image manifest crashes the dockerd daemon. Versions 20.10.3 and 19.03.15 contain patches that prevent the daemon from crashing. |
Affected by 2 other vulnerabilities. |
|
VCID-f3ee-8awp-aaaa
Aliases: CVE-2014-5282 |
Docker before 1.3 does not properly validate image IDs, which allows remote attackers to redirect to another image through the loading of untrusted images via 'docker load'. |
Affected by 19 other vulnerabilities. |
|
VCID-fckq-6rf5-aaaf
Aliases: CVE-2021-41092 GHSA-99pg-grm5-qq3v |
Docker CLI is the command line interface for the docker container runtime. A bug was found in the Docker CLI where running `docker login my-private-registry.example.com` with a misconfigured configuration file (typically `~/.docker/config.json`) listing a `credsStore` or `credHelpers` that could not be executed would result in any provided credentials being sent to `registry-1.docker.io` rather than the intended private registry. This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as soon as possible. For users unable to update ensure that any configured credsStore or credHelpers entries in the configuration file reference an installed credential helper that is executable and on the PATH. |
Affected by 0 other vulnerabilities. |
|
VCID-funr-5s9t-aaak
Aliases: CVE-2016-9962 GHSA-gp4j-w3vj-7299 |
RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container. |
Affected by 16 other vulnerabilities. |
|
VCID-kan2-3fe2-aaan
Aliases: CVE-2020-15157 GHSA-742w-89gc-8m9c |
In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user's username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected. |
Affected by 5 other vulnerabilities. |
|
VCID-mgf4-u476-aaar
Aliases: CVE-2014-9356 GHSA-vj3f-3286-r4pf |
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. |
Affected by 19 other vulnerabilities. |
|
VCID-nb9z-axvx-aaan
Aliases: CVE-2017-16539 |
The DefaultLinuxSpec function in oci/defaults.go in Docker Moby through 17.03.2-ce does not block /proc/scsi pathnames, which allows attackers to trigger data loss (when certain older Linux kernels are used) by leveraging Docker container access to write a "scsi remove-single-device" line to /proc/scsi/scsi, aka SCSI MICDROP. |
Affected by 13 other vulnerabilities. |
|
VCID-njzy-fg53-aaac
Aliases: CVE-2018-10892 |
The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardware like enabling/disabling bluetooth or turning up/down keyboard brightness. |
Affected by 13 other vulnerabilities. |
|
VCID-pv9f-a31y-aaac
Aliases: CVE-2015-3630 GHSA-8fvr-5rqf-3wwh |
Docker Engine before 1.6.1 uses weak permissions for (1) /proc/asound, (2) /proc/timer_stats, (3) /proc/latency_stats, and (4) /proc/fs, which allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. |
Affected by 19 other vulnerabilities. Affected by 20 other vulnerabilities. |
|
VCID-q2y6-4n1b-aaae
Aliases: CVE-2014-5277 GHSA-8w94-cf6g-c8mg GO-2022-0636 PYSEC-2014-80 |
Docker before 1.3.1 and docker-py before 0.5.3 fall back to HTTP when the HTTPS connection to the registry fails, which allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic. |
Affected by 19 other vulnerabilities. |
|
VCID-q64b-tmvc-aaan
Aliases: CVE-2018-20699 |
Docker Engine before 18.09 allows attackers to cause a denial of service (dockerd memory consumption) via a large integer in a --cpuset-mems or --cpuset-cpus value, related to daemon/daemon_unix.go, pkg/parsers/parsers.go, and pkg/sysinfo/sysinfo.go. |
Affected by 10 other vulnerabilities. |
|
VCID-qeds-t2du-aaae
Aliases: CVE-2014-8179 |
Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 does not properly validate and extract the manifest object from its JSON representation during a pull, which allows attackers to inject new attributes in a JSON object and bypass pull-by-digest validation. |
Affected by 18 other vulnerabilities. |
|
VCID-r9sc-d8bp-aaak
Aliases: CVE-2019-13509 GHSA-j249-ghv5-7mxv |
In Docker CE and EE before 18.09.8 (as well as Docker EE before 17.06.2-ee-23 and 18.x before 18.03.1-ee-10), Docker Engine in debug mode may sometimes add secrets to the debug log. This applies to a scenario where docker stack deploy is run to redeploy a stack that includes (non external) secrets. It potentially applies to other API users of the stack API if they resend the secret. |
Affected by 7 other vulnerabilities. |
|
VCID-rtmc-4r84-aaas
Aliases: CVE-2019-5736 |
runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe. |
Affected by 12 other vulnerabilities. |
|
VCID-th43-scy8-aaab
Aliases: CVE-2021-21284 GHSA-7452-xqpj-6rpc |
In Docker before versions 9.03.15, 20.10.3 there is a vulnerability involving the --userns-remap option in which access to remapped root allows privilege escalation to real root. When using "--userns-remap", if the root user in the remapped namespace has access to the host filesystem they can modify files under "/var/lib/docker/<remapping>" that cause writing files with extended privileges. Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user. |
Affected by 2 other vulnerabilities. |
|
VCID-w2s9-abux-aaae
Aliases: CVE-2014-9358 GHSA-qmmc-jppf-32wv |
Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications." |
Affected by 19 other vulnerabilities. |
|
VCID-wgvq-269b-aaaq
Aliases: CVE-2020-13401 GHSA-qrrc-ww9x-r43g |
An issue was discovered in Docker Engine before 19.03.11. An attacker in a container, with the CAP_NET_RAW capability, can craft IPv6 router advertisements, and consequently spoof external IPv6 hosts, obtain sensitive information, or cause a denial of service. |
Affected by 2 other vulnerabilities. |
|
VCID-x781-mkbk-aaak
Aliases: CVE-2018-12608 GHSA-qrqr-3x5j-2xw9 |
An issue was discovered in Docker Moby before 17.06.0. The Docker engine validated a client TLS certificate using both the configured client CA root certificate and all system roots on non-Windows systems. This allowed a client with any domain validated certificate signed by a system-trusted root CA (as opposed to one signed by the configured CA root certificate) to authenticate. |
Affected by 13 other vulnerabilities. |
|
VCID-y54c-1hy4-aaad
Aliases: CVE-2014-0048 |
An issue was found in Docker before 1.6.0. Some programs and scripts in Docker are downloaded via HTTP and then executed or used in unsafe ways. |
Affected by 19 other vulnerabilities. Affected by 18 other vulnerabilities. |
|
VCID-ydxd-x5uj-aaab
Aliases: CVE-2019-13139 |
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. |
Affected by 9 other vulnerabilities. |
|
VCID-ymjf-n7j4-aaag
Aliases: CVE-2015-3627 GHSA-g7v2-2qxx-wjrw |
Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image. |
Affected by 19 other vulnerabilities. Affected by 20 other vulnerabilities. |
|
VCID-z1mx-h6b5-aaae
Aliases: CVE-2019-1020014 |
docker-credential-helpers before 0.6.3 has a double free in the List functions. |
Affected by 6 other vulnerabilities. Affected by 6 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|