rpm package
suse/docker-stable&distro=SUSE Linux Enterprise Module for Containers 15 SP7
pkg:rpm/suse/docker-stable&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Containers%2015%20SP7
Vulnerabilities (59)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2018-16875 | Med | 5.9 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 14, 2018 | The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates | |
| CVE-2018-16874 | Hig | 8.1 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 14, 2018 | In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but | |
| CVE-2018-16873 | Hig | 8.1 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 14, 2018 | In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPA | |
| CVE-2018-10892 | Med | 5.3 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Jul 6, 2018 | 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. | |
| CVE-2017-16539 | Med | 5.9 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Nov 4, 2017 | 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-dev | |
| CVE-2017-14992 | Med | 6.5 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Nov 1, 2017 | 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-2016-9962 | Med | 6.4 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Jan 31, 2017 | 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 conta | |
| CVE-2016-8867 | Hig | 7.5 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Oct 28, 2016 | 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-2016-3697 | Hig | 7.8 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Jun 1, 2016 | 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-2015-3631 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | May 18, 2015 | 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. | ||
| CVE-2015-3630 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | May 18, 2015 | 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. | ||
| CVE-2015-3629 | Hig | 7.8 | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | May 18, 2015 | 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. | |
| CVE-2015-3627 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | May 18, 2015 | 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. | ||
| CVE-2014-9358 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 16, 2014 | 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." | ||
| CVE-2014-9357 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 16, 2014 | Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the chroot for archive extraction. | ||
| CVE-2014-6408 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 12, 2014 | 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 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Dec 12, 2014 | 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. | ||
| CVE-2014-5277 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Nov 17, 2014 | 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 | ||
| CVE-2014-3499 | — | < 24.0.9_ce-150000.1.25.1 | 24.0.9_ce-150000.1.25.1 | Jul 11, 2014 | 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. |
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPA
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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 < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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-dev
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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 < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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 conta
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
- affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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-2015-3631May 18, 2015affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
- CVE-2015-3630May 18, 2015affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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 < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
- CVE-2015-3627May 18, 2015affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
- CVE-2014-9358Dec 16, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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."
- CVE-2014-9357Dec 16, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build in a Dockerfile in an LZMA (.xz) archive, related to the chroot for archive extraction.
- CVE-2014-6408Dec 12, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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-6407Dec 12, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
- CVE-2014-5277Nov 17, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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
- CVE-2014-3499Jul 11, 2014affected < 24.0.9_ce-150000.1.25.1fixed 24.0.9_ce-150000.1.25.1
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.
Page 3 of 3