Search for packages
| purl | pkg:deb/debian/docker.io@18.09.1%2Bdfsg1-7.1%2Bdeb10u3 |
| Next non-vulnerable version | 20.10.24+dfsg1-1 |
| Latest non-vulnerable version | 26.1.5+dfsg1-9 |
| Risk | 4.5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3eju-5upk-auhy
Aliases: CVE-2021-41089 GHSA-v994-f8vw-g7j4 |
`docker cp` allows unexpected chmod of host files in Moby Docker Engine ## Impact 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. ## Patches 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. ## Workarounds Ensure you only run trusted containers. ## Credits The Moby project would like to thank Lei Wang and Ruizhi Xiao for responsibly disclosing this issue in accordance with the [Moby security policy](https://github.com/moby/moby/blob/master/SECURITY.md). ## For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/moby/moby/issues/new) * Email us at security@docker.com if you think you’ve found a security bug |
Affected by 10 other vulnerabilities. |
|
VCID-41ft-14gt-bbbq
Aliases: CVE-2024-41110 GHSA-v23v-6jw2-98fq |
Authz zero length regression A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass [authorization plugins (AuthZ)](https://docs.docker.com/engine/extend/plugins_authorization/) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users. ### Impact Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an [authorization plugin](https://docs.docker.com/engine/extend/plugins_authorization/) without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it. A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine [v18.09.1](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-1) in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted. Docker EE v19.03.x and all versions of Mirantis Container Runtime **are not vulnerable.** ### Vulnerability details - **AuthZ bypass and privilege escalation:** An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly. - **Initial fix:** The issue was fixed in Docker Engine [v18.09.1](https://docs.docker.com/engine/release-notes/18.09/#security-fixes-1) January 2019.. - **Regression:** The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned [CVE-2024-41110](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41110). ### Patches - docker-ce v27.1.1 containes patches to fix the vulnerability. - Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches. ### Remediation steps - If you are running an affected version, update to the most recent patched version. - Mitigation if unable to update immediately: - Avoid using AuthZ plugins. - Restrict access to the Docker API to trusted parties, following the principle of least privilege. ### References - https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb - https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1 - https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/ |
Affected by 0 other vulnerabilities. |
|
VCID-6vru-hsfs-rufg
Aliases: CVE-2020-15257 GHSA-36xw-fx78-c5r4 |
Multiple vulnerabilities have been found in containerd, the worst of which could result in privilege escalation. |
Affected by 4 other vulnerabilities. |
|
VCID-bhju-575k-ebh3
Aliases: CVE-2021-41092 GHSA-99pg-grm5-qq3v |
Docker CLI leaks private registry credentials to registry-1.docker.io ## Impact 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. ## Patches This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as soon as possible. ## Workarounds Ensure that any configured `credsStore` or `credHelpers` entries in the configuration file reference an installed credential helper that is executable and on the `PATH`. ## For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/docker/cli/issues/new/choose) * Email us at security@docker.com if you think you’ve found a security bug |
Affected by 10 other vulnerabilities. |
|
VCID-e9ng-x516-53cf
Aliases: CVE-2021-41091 GHSA-3fwx-pjgw-3558 |
Moby (Docker Engine) Insufficiently restricted permissions on data directory ## Impact A bug was found in Moby (Docker Engine) where the data directory (typically `/var/lib/docker`) contained subdirectories with insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as `setuid`), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files. ## Patches This bug has been fixed in Moby (Docker Engine) 20.10.9. Users should update to this version as soon as possible. Running containers should be stopped and restarted for the permissions to be fixed. ## Workarounds Limit access to the host to trusted users. Limit access to host volumes to trusted containers. ## Credits The Moby project would like to thank Joan Bruguera for responsibly disclosing this issue in accordance with the [Moby security policy](https://github.com/moby/moby/blob/master/SECURITY.md). ## For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/moby/moby/issues/new) * Email us at security@docker.com if you think you’ve found a security bug |
Affected by 10 other vulnerabilities. |
|
VCID-gbw6-3a59-mbhu
Aliases: CVE-2020-15157 GHSA-742w-89gc-8m9c |
containerd v1.2.x can be coerced into leaking credentials during image pull ## Impact 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 rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N. ## Patches This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. ## Workarounds 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. ## Credits The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md). |
Affected by 4 other vulnerabilities. |
|
VCID-gund-83cy-9fap
Aliases: CVE-2021-21284 GHSA-7452-xqpj-6rpc |
moby Access to remapped root allows privilege escalation to real root ### Impact 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. ### Patches Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user. ### Credits Maintainers would like to thank Alex Chapman for discovering the vulnerability; @awprice, @nathanburrell, @raulgomis, @chris-walz, @erin-jensby, @bassmatt, @mark-adams, @dbaxa for working on it and Zac Ellis for responsibly disclosing it to security@docker.com |
Affected by 4 other vulnerabilities. |
|
VCID-h83p-v26k-s7fa
Aliases: CVE-2020-13401 GHSA-qrrc-ww9x-r43g |
A flaw in Docker allowed possible information leakage. |
Affected by 4 other vulnerabilities. |
|
VCID-pevy-d197-zydv
Aliases: CVE-2019-14271 GHSA-v2cv-wwxq-qq97 |
Moby Docker cp broken with debian containers 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. |
Affected by 4 other vulnerabilities. |
|
VCID-u44m-mgza-nfcx
Aliases: CVE-2019-13509 GHSA-j249-ghv5-7mxv |
Secret insertion into debug log in Docker 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 4 other vulnerabilities. |
|
VCID-uckr-kzdf-7ydj
Aliases: CVE-2021-21285 GHSA-6fj5-m822-rqx8 |
moby docker daemon crash during image pull of malicious image ### Impact Pulling an intentionally malformed Docker image manifest crashes the `dockerd` daemon. ### Patches Versions 20.10.3 and 19.03.15 contain patches that prevent the daemon from crashing. ### Credits Maintainers would like to thank Josh Larsen, Ian Coldwater, Duffie Cooley, Rory McCune for working on the vulnerability and Brad Geesaman for responsibly disclosing it to security@docker.com. |
Affected by 4 other vulnerabilities. |
|
VCID-yt33-nmzd-r3cs
Aliases: CVE-2019-13139 |
docker: command injection due to a missing validation of the git ref command |
Affected by 4 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-165g-hgmx-nybk | Information Exposure in RunC 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. |
CVE-2016-9962
GHSA-gp4j-w3vj-7299 |
| VCID-43es-2d6x-jba8 | docker: container breakout without selinux in enforcing mode |
CVE-2018-10892
|
| VCID-6vru-hsfs-rufg | Multiple vulnerabilities have been found in containerd, the worst of which could result in privilege escalation. |
CVE-2020-15257
GHSA-36xw-fx78-c5r4 |
| VCID-ahbf-gwnw-nufp | Docker Moby /proc/scsi Path Exposure Allows Host Data Loss (SCSI MICDROP) 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. |
CVE-2017-16539
GHSA-vfjc-2qcw-j95j |
| VCID-e6sp-khpk-r3d8 | docker: Manifest validation and parsing logic errors allow pull-by-digest validation bypass |
CVE-2014-8179
|
| VCID-eb24-pguf-ryg1 | tar-split memory exhaustion 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. |
CVE-2017-14992
GHSA-hqwh-8xv9-42hw |
| VCID-f6d3-yyvz-xqgs | docker: Memory exhaustion via large integer used with --cpuset-mems or --cpuset-cpus |
CVE-2018-20699
|
| VCID-gbw6-3a59-mbhu | containerd v1.2.x can be coerced into leaking credentials during image pull ## Impact 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 rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N. ## Patches This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. ## Workarounds 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. ## Credits The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md). |
CVE-2020-15157
GHSA-742w-89gc-8m9c |
| VCID-gund-83cy-9fap | moby Access to remapped root allows privilege escalation to real root ### Impact 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. ### Patches Versions 20.10.3 and 19.03.15 contain patches that prevent privilege escalation from remapped user. ### Credits Maintainers would like to thank Alex Chapman for discovering the vulnerability; @awprice, @nathanburrell, @raulgomis, @chris-walz, @erin-jensby, @bassmatt, @mark-adams, @dbaxa for working on it and Zac Ellis for responsibly disclosing it to security@docker.com |
CVE-2021-21284
GHSA-7452-xqpj-6rpc |
| VCID-h83p-v26k-s7fa | A flaw in Docker allowed possible information leakage. |
CVE-2020-13401
GHSA-qrrc-ww9x-r43g |
| VCID-pevy-d197-zydv | Moby Docker cp broken with debian containers 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. |
CVE-2019-14271
GHSA-v2cv-wwxq-qq97 |
| VCID-qwqe-27yu-8kds | Docker Authentication Bypass 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. |
CVE-2018-12608
GHSA-qrqr-3x5j-2xw9 |
| VCID-sh5d-p485-6qh4 | docker: symlink-exchange race attacks in docker cp |
CVE-2018-15664
|
| VCID-su25-rgw1-xkg6 | docker: Attacker controlled layer IDs lead to local graph content poisoning |
CVE-2014-8178
|
| VCID-u44m-mgza-nfcx | Secret insertion into debug log in Docker 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. |
CVE-2019-13509
GHSA-j249-ghv5-7mxv |
| VCID-uckr-kzdf-7ydj | moby docker daemon crash during image pull of malicious image ### Impact Pulling an intentionally malformed Docker image manifest crashes the `dockerd` daemon. ### Patches Versions 20.10.3 and 19.03.15 contain patches that prevent the daemon from crashing. ### Credits Maintainers would like to thank Josh Larsen, Ian Coldwater, Duffie Cooley, Rory McCune for working on the vulnerability and Brad Geesaman for responsibly disclosing it to security@docker.com. |
CVE-2021-21285
GHSA-6fj5-m822-rqx8 |
| VCID-yt33-nmzd-r3cs | docker: command injection due to a missing validation of the git ref command |
CVE-2019-13139
|