This script is Copyright (C) 2017 Tenable Network Security, Inc.
The remote Red Hat host is missing one or more security updates.
An update for docker is now available for Red Hat Enterprise Linux 7
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.
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.
The following packages have been upgraded to a newer upstream version:
docker (1.12.5). (BZ#1404298)
Security Fix(es) :
* The runc component used by `docker exec` feature of docker allowed
additional container processes via to be ptraced by the pid 1 of the
container. This allows the main processes of the container, if running
as root, to gain low-level access to these new processes during
initialization. An attacker can, depending on the nature of the
incoming process, leverage this to elevate access to the host. This
ranges from accessing host content through the file descriptors of the
incoming process to, potentially, a complete container escape by
leveraging memory access or syscall interception. (CVE-2016-9962)
Red Hat would like to thank the Docker project for reporting this
issue. Upstream acknowledges Aleksa Sarai (SUSE) and Tonis Tiigi
(Docker) as the original reporters.
Bug Fix(es) :
* The docker containers and images did not read proxy variables from
the environment when contacting registries. As a consequence, a user
could not pull image when the system was configured to use a proxy.
The containers and images have been fixed to read proxy variables from
the environment, and pulling images now from a system with a proxy
works correctly. (BZ#1393816)
* Occasionally the docker-storage-setup service could start before a
thin pool is ready which caused it to failed. As a consequence, the
docker daemon also failed. This bug has been fixed and now
docker-storage-setup waits for a thin pool to be created for 60
seconds. This default time can be configured. As a result, docker and
docker-storage-setup start correctly upon reboot. (BZ#1316786)
* Previously, the docker daemon's unit file was not supplying the
userspace proxy path. As a consequence, containers that exposed ports
could not be started. To fix this bug, the unit file was updated to
include the userspace proxy path option to the daemon start command,
along with several other minor packaging fixes. As a result,
containers that expose ports can now be started as expected.
* Previously, the system CA (Certificate Authority) pool was excluded
when the registry CA is used from the /etc/docker/certs.d/ directory.
As a consequence, pulling images failed with the following error :
Failed to push image: x509: certificate signed by unknown authority
This bug has been fixed and docker now reads the system CA pool
correctly and pulling images now work correctly. (BZ#1400372)
* Previously, the docker daemon option did not handle correctly the
'--block-registry docker.io' option. As a consequence, docker allowed
pulling images from docker.io even when the '--block-registry
docker.io' option was enabled. This update fixed the handling of the
option, and now using '--block-registry docker.io' correctly blocks
image pulling. (BZ#1395401)
See also :
Update the affected packages.
Risk factor :
Medium / CVSS Base Score : 4.4
CVSS Temporal Score : 3.3
Public Exploit Available : false