Summary
This update for docker, docker-runc, containerd, golang-github-docker-libnetwork fixes several issues.
These security issues were fixed:
- CVE-2017-16539: The DefaultLinuxSpec function in oci/defaults.go docker did
not block /proc/scsi pathnames, which allowed 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 (bnc#1066801)
- CVE-2017-14992: Lack of content verification in docker allowed a remote
attacker to cause a Denial of Service via a crafted image layer payload, aka
gzip bombing. (bnc#1066210)
These non-security issues were fixed:
- bsc#1059011: The systemd service helper script used a timeout of 60 seconds to start the daemon, which is insufficient in cases where the daemon takes longer to start. Instead, set the service type from 'simple' to 'notify' and remove the now superfluous helper script.
- bsc#1057743: New requirement with new version of docker-libnetwork.
- bsc#1032287: Missing docker systemd configuration.
- bsc#1057743: New 'symbol' for libnetwork requirement.
- bsc#1057743: Update secrets patch to handle 'old' containers that have orphaned secret data no longer available on the host.
- bsc#1055676: Update patches to correctly handle volumes and mounts when Docker is running with user namespaces enabled.
- bsc#1045628:: Add patch to make the dm storage driver remove a container's rootfs mountpoint before attempting to do libdm operations on it. This helps avoid complications when live mounts will leak into containers.
- bsc#1069758: Upgrade Docker to v17.09.1_ce (and obsolete docker-image-migrator).
- bsc#1021227: bsc#1029320 bsc#1058173 -- Enable docker devicemapper support for deferred removal/deletion within Containers module.
- bsc#1046024: Correct interaction between Docker and SuSEFirewall2, to avoid breaking Docker networking after boot.
- bsc#1048046: Build with -buildmode=pie to make all binaries PIC.
- bsc#1072798: Remove dependency on obsolete bridge-utils.
- bsc#1064926: Set --start-timeout=2m by default to match upstream.
- bsc#1065109, bsc#1053532: Use the upstream makefile so that Docker can get the commit ID in `docker info`.
Please note that the 'docker-runc' package is just a rename of the old 'runc' package to match that we now ship the Docker fork of runc.
Fixed packages 8
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 Linux Enterprise Module for Containers 12 | containerd | 0.2.9+gitr706_06b9cb351610-16.8.1 |
| SUSE · SLES 12 Linux Enterprise Module for Containers 12 | docker | 17.09.1_ce-98.8.1 |
| SUSE · SLES 12 Linux Enterprise Module for Containers 12 | docker-runc | 1.0.0rc4+gitr3338_3f2f8b84a77f-1.3.1 |
| SUSE · SLES 12 Linux Enterprise Module for Containers 12 | golang-github-docker-libnetwork | 0.7.0.1+gitr2066_7b2b1feb1de4-10.1 |
| SUSE · OpenStack Cloud 6 | containerd | 0.2.9+gitr706_06b9cb351610-16.8.1 |
| SUSE · OpenStack Cloud 6 | docker | 17.09.1_ce-98.8.1 |
| SUSE · OpenStack Cloud 6 | docker-runc | 1.0.0rc4+gitr3338_3f2f8b84a77f-1.3.1 |
| SUSE · OpenStack Cloud 6 | golang-github-docker-libnetwork | 0.7.0.1+gitr2066_7b2b1feb1de4-10.1 |
Vulnerabilities 2
-
Medium 6.5
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 g…
-
Medium 5.9
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 "s…
References
-
report
https://bugzilla.suse.com/1021227
-
report
https://bugzilla.suse.com/1029320
-
report
https://bugzilla.suse.com/1032287
-
report
https://bugzilla.suse.com/1045628
-
report
https://bugzilla.suse.com/1046024
-
report
https://bugzilla.suse.com/1048046
-
report
https://bugzilla.suse.com/1051429
-
report
https://bugzilla.suse.com/1053532
-
report
https://bugzilla.suse.com/1055676
-
report
https://bugzilla.suse.com/1057743
-
report
https://bugzilla.suse.com/1058173
-
report
https://bugzilla.suse.com/1059011
-
report
https://bugzilla.suse.com/1064926
-
report
https://bugzilla.suse.com/1065109
-
report
https://bugzilla.suse.com/1066210
-
report
https://bugzilla.suse.com/1066801
-
report
https://bugzilla.suse.com/1069468
-
report
https://bugzilla.suse.com/1069758
-
report
https://bugzilla.suse.com/1072798
-
web
https://www.suse.com/security/cve/CVE-2017-14992
-
web
https://www.suse.com/security/cve/CVE-2017-16539