Synopsis

Moderate: docker security, bug fix, and enhancement update

Type/Severity

Security Advisory: Moderate

Topic

An update for docker is now available for Red Hat Enterprise Linux 7 Extras.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Description

Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.

Security Fix(es):

• It was found that Docker would launch containers under the specified UID instead of a username. An attacker able to launch a container could use this flaw to escalate their privileges to root within the launched container. (CVE-2016-3697)
  

This issue was discovered by Mrunal Patel (Red Hat).

Bug Fix(es):

• The process of pulling an image spawns a new "goroutine" for each layer in the image manifest. If any of these downloads, everything stops and an error is returned, even though other goroutines would still be running and writing output through a progress reader which is attached to an http response writer. Since the request handler had already returned from the first error, the http server panics when one of these download goroutines makes a write to the response writer buffer. This bug has been fixed, and docker no longer panics when pulling an image. (BZ#1264562)
  
• Previously, in certain situations, a container rootfs remained busy during container removal. This typically happened if a container mount point leaked into another mount namespace. As a consequence, container removal failed. To fix this bug, a new docker daemon option "dm.use_deferred_deletion" has been provided. If set to true, this option will defer the container rootfs deletion. The user will see success on container removal but the actual thin device backing the rootfs will be deleted later when it is not busy anymore. (BZ#1190492)
  
• Previously, the Docker unit file had the "Restart" option set to "on-failure". Consequently, the docker daemon was forced to restart even in cases where it couldn't be started because of configuration or other issues and this situation forced unnecessary restarts of the docker-storage-setup service in a loop. This also caused real error messages to be lost due to so many restarts. To fix this bug, "Restart=on-failure" has been replaced with "Restart=on-abnormal" in the docker unit file. As a result, the docker daemon will not automatically restart if it fails with an unclean exit code. (BZ#1319783)
  
• Previously, the request body was incorrectly read twice by the docker daemon and consequently, an EOF error was returned. To fix this bug, the code which incorrectly read the request body the first time has been removed. As a result, the EOF error is no longer returned and the body is correctly read when really needed. (BZ#1329743)
  

Enhancement(s):

• The /usr/bin/docker script now calls /usr/bin/docker-current or /usr/bin/docker-latest based on the value of the sysconfig variable DOCKERBINARY present in /etc/sysconfig/docker. /usr/bin/docker and /etc/sysconfig/docker provided by the docker-common package allow the admin to configure which docker client binary gets called. /usr/bin/docker will call /usr/bin/docker-latest by default when docker is not installed. If docker is installed, /usr/bin/docker will call /usr/bin/docker-current by default, unless DOCKERBINARY is set to /usr/bin/docker-latest in /etc/sysconfig/docker. This way, you can use docker-latest or docker without the need to check which version of the daemon is currently running. (BZ#1328219)

Solution

For details on how to apply this update, which includes the changes described in this advisory, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 7 x86_64
• Red Hat Enterprise Linux Server from RHUI 7 x86_64

Fixes

• BZ - 1186066 - The docker stop operation doesn't work with --pid=host containers containing multiple processes
• BZ - 1261565 - docker-storage-setup service fails after initial successful run if DEVS is defined in /etc/sysconfig/docker-storage-setup
• BZ - 1266307 - Capture information about the remote user connecting over socket in /run/docker
• BZ - 1268059 - docker exec setting the wrong cgroups
• BZ - 1272143 - Can't start containers that use supplemental groups but lack /etc/groups
• BZ - 1303110 - [extras-rhel-7.2.4] Docker does not own /usr/lib/docker-storage-setup
• BZ - 1309739 - docker push fails when pushing image to docker hub
• BZ - 1316651 - Docker run read-only: System error: read-only file system
• BZ - 1319783 - [docker] Use Restart=on-abnormal instead of Restart=on-failure
• BZ - 1322762 - sha256 Conflict while pull images after upgrade
• BZ - 1328219 - [extras-rhel-7.2.4] include docker-common subpackage in 'docker' to handle /usr/bin/docker for docker and docker-latest
• BZ - 1329423 - Skip /dev setup in container when it is bind mounted in
• BZ - 1329450 - CVE-2016-3697 docker: privilege escalation via confusion of usernames and UIDs
• BZ - 1329743 - Unable to push images to private registry using docker-1.9.1-25 and python-docker-py-1.7.2-1
• BZ - 1330595 - /usr/bin/docker wrapper script: $@ must be quoted
• BZ - 1330622 - enhance condition judgement in /usr/bin/docker script
• BZ - 1331007 - SELinux regression in docker-selinux-1.9.1-37
• BZ - 1332592 - Incomplete requirement on docker-common

CVEs

• CVE-2016-3697

References

• http://www.redhat.com/security/updates/classification/#normal

Red Hat Enterprise Linux Server 7

SRPM
docker-1.9.1-40.el7.src.rpm	SHA-256: 5094f52d629de16ac8575080ebc8a381a86f0b6c7442ac3f0e28e757af8794a7
x86_64
docker-1.9.1-40.el7.x86_64.rpm	SHA-256: 612cac2adf9c31358e58370dbc4967cd0e8f935a8000387486a0d614e9808806
docker-common-1.9.1-40.el7.x86_64.rpm	SHA-256: af0ee44fbd11a27dc4044820982d599ef25486ccf02ad7131226e773988fbd5b
docker-forward-journald-1.9.1-40.el7.x86_64.rpm	SHA-256: 8382cf1a0231cba93671c20fc281ea0aad01955170b0822a05491923d9892b60
docker-logrotate-1.9.1-40.el7.x86_64.rpm	SHA-256: da8b204bb1f3ddaa592525ac1ed5636e355ced8c70236d5cbed8211a2062d7f3
docker-selinux-1.9.1-40.el7.x86_64.rpm	SHA-256: e6d20e7bccf85885d5264a6cccb2078e803dbc5ff085766ecd2935ea239cfabc

Red Hat Enterprise Linux Server from RHUI 7

SRPM
docker-1.9.1-40.el7.src.rpm	SHA-256: 5094f52d629de16ac8575080ebc8a381a86f0b6c7442ac3f0e28e757af8794a7
x86_64
docker-1.9.1-40.el7.x86_64.rpm	SHA-256: 612cac2adf9c31358e58370dbc4967cd0e8f935a8000387486a0d614e9808806
docker-common-1.9.1-40.el7.x86_64.rpm	SHA-256: af0ee44fbd11a27dc4044820982d599ef25486ccf02ad7131226e773988fbd5b
docker-forward-journald-1.9.1-40.el7.x86_64.rpm	SHA-256: 8382cf1a0231cba93671c20fc281ea0aad01955170b0822a05491923d9892b60
docker-logrotate-1.9.1-40.el7.x86_64.rpm	SHA-256: da8b204bb1f3ddaa592525ac1ed5636e355ced8c70236d5cbed8211a2062d7f3
docker-selinux-1.9.1-40.el7.x86_64.rpm	SHA-256: e6d20e7bccf85885d5264a6cccb2078e803dbc5ff085766ecd2935ea239cfabc