Docker

Docker Desktop before 4.5.1 on Windows allows attackers to move arbitrary files. NOTE: this issue exists because of an incomplete fix for CVE-2022-23774.

Published: 2022-02-19T01:56:06.000Z
Updated: 2024-08-03T04:36:06.950Z

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.

Published: 2021-02-02T17:55:16.000Z
Updated: 2024-08-03T18:09:15.012Z

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.

Published: 2021-02-02T17:55:22.000Z
Updated: 2024-08-03T18:09:15.042Z

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.

Published: 2020-12-30T22:28:10.000Z
Updated: 2024-08-04T16:18:44.387Z

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.

Published: 2019-02-11T00:00:00.000Z
Updated: 2024-08-04T20:01:52.208Z

In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the nsswitch facility dynamically loads a library inside a chroot that contains the contents of the container.

Published: 2019-07-29T17:05:57.000Z
Updated: 2024-08-05T00:12:43.386Z

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.

Published: 2017-01-31T22:00:00.000Z
Updated: 2024-08-06T03:07:31.309Z

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.

Published: 2016-06-01T20:00:00.000Z
Updated: 2024-08-06T00:03:34.441Z

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.

Published: 2015-05-18T15:00:00.000Z
Updated: 2024-08-06T05:47:57.906Z

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.

Published: 2015-05-18T15:00:00.000Z
Updated: 2024-08-06T05:47:57.807Z

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.

Published: 2015-05-18T15:00:00.000Z
Updated: 2024-08-06T05:47:57.723Z

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."

Published: 2014-12-16T18:00:00.000Z
Updated: 2024-08-06T13:40:25.168Z

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.

Published: 2019-12-02T17:07:40.000Z
Updated: 2024-08-06T13:40:25.025Z

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.

Published: 2019-12-04T15:10:35.000Z
Updated: 2024-08-06T13:10:51.252Z

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.

Published: 2019-12-04T15:05:02.000Z
Updated: 2024-08-06T13:10:51.117Z

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.

Published: 2014-12-12T15:00:00.000Z
Updated: 2024-08-06T12:17:23.673Z

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'.

Published: 2018-02-06T16:00:00.000Z
Updated: 2024-08-06T11:41:47.960Z

A vulnerability exists in Docker before 1.2 via container names, which may collide with and override container IDs.

Published: 2020-02-07T17:03:36.000Z
Updated: 2024-08-06T11:41:47.771Z

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.

Published: 2014-11-17T16:00:00.000Z
Updated: 2024-08-06T11:41:47.966Z

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.

Published: 2020-01-02T16:22:06.000Z
Updated: 2024-08-06T09:05:37.067Z

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

Published: 2017-10-06T15:00:00.000Z
Updated: 2024-08-06T09:05:37.067Z