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.

This docker version upgrade fixes the following security and non security issues, and adds the also additional features :

  - Updated to 1.4.1 (2014-12-15) :

  - Runtime :

  - Fix issue with volumes-from and bind mounts not being     honored after create (fixes bnc#913213)

  - Added e2fsprogs as runtime dependency, this is required     when the devicemapper driver is used. (bnc#913211).

  - Fixed owner & group for docker.socket (thanks to Andrei     Dziahel and     https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752555     #5)

  - Updated to 1.4.0 (2014-12-11) :

  - Notable Features since 1.3.0 :

  - Set key=value labels to the daemon (displayed in `docker     info`), applied with new `-label` daemon flag

  - Add support for `ENV` in Dockerfile of the form: `ENV     name=value name2=value2...`

  - New Overlayfs Storage Driver

  - `docker info` now returns an `ID` and `Name` field

  - Filter events by event name, container, or image

  - `docker cp` now supports copying from container volumes

  - Fixed `docker tag`, so it honors `--force` when     overriding a tag for existing image.

  - Changes introduced by 1.3.3 (2014-12-11) :

  - Security :

  - Fix path traversal vulnerability in processing of     absolute symbolic links (CVE-2014-9356) - (bnc#909709)

  - Fix decompression of xz image archives, preventing     privilege escalation (CVE-2014-9357) - (bnc#909710)

  - Validate image IDs (CVE-2014-9358) - (bnc#909712)

  - Runtime :

  - Fix an issue when image archives are being read slowly

  - Client :

  - Fix a regression related to stdin redirection

  - Fix a regression with `docker cp` when destination is     the current directory

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Updated docker packages that fix two security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 7 Extras.

Red Hat Product Security has rated this update as having Low security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Docker is a service providing container management on Linux.

It was found that a malicious container image could overwrite arbitrary portions of the host file system by including absolute symlinks, potentially leading to privilege escalation. (CVE-2014-9356)

A flaw was found in the way the Docker service unpacked images or builds after a 'docker pull'. An attacker could use this flaw to provide a malicious image or build that, when unpacked, would escalate their privileges on the system. (CVE-2014-9357)

Red Hat would like to thank Docker Inc. for reporting these issues.

The docker-python subpackage provides the new Atomic tool. The goal of Atomic is to provide a high level, coherent entry point for Red Hat Enterprise Linux Atomic Host. Atomic makes it easier to interact with special kinds of containers, such as super-privileged debugging tools.
Comprehensive information and documentation is available in the atomic manual pages.

The docker packages have been upgraded to upstream version 1.4.1, which provides a number of bug fixes and enhancements over the previous version, most notably an experimental overlayfs storage driver. (BZ#1174351)

Bug fixes :

* The JSON configuration files for containers and images were inconsistent. As a consequence, when these files were parsed by the 'docker inspect' command, the output was unnecessarily complex. This update improves the key naming schema in the configuration files and the output from 'docker inspect' is now uniform. (BZ#1092773)

* The /run directory had an incorrect SELinux label. As a consequence, containers could not access /run. This update corrects the SELinux label and containers now have access to /run. (BZ#1100009)

* The Docker service contained an incorrect path for the secrets directory. As a consequence, executing 'docker run' failed to create containers. This update fixes the default path to the secrets directory and 'docker run' now executes successfully. (BZ#1102568)

* It was not possible to specify a default repository in the configuration file in cases where all docker.io files are inaccessible. As a consequence, running docker commands failed because they could not contact the default repositories. Now, it is possible to specify a local Docker repository, and commands no longer fail because they are able to connect to a local private repository.
(BZ#1106430)

* When executing the 'docker attach' command on a container which was in the process of shutting down, the process did not fail, but became unresponsive. This bug has been fixed, and running 'docker attach' on a container which is shutting down causes the attach process to fail with an informative error message that it is not possible to attach to a stopped container. (BZ# 1113608)

* The 'docker run' sub-command incorrectly returned non-zero exit codes, when they all should have been zero. As a consequence, it was not possible to differentiate between the exit codes of the docker command line and exit codes of contained processes, which in turn made automated control of 'docker run' impossible. This update fixes the inconsistencies within the exit codes of 'docker run'. Additionally, this update also fixes inconsistencies of other docker sub-commands and improves the language in the error and warning messages.
(BZ#1162807)

* Adding a new registry with the '--registry-prepend' option did not follow the correct order to query and download an image. As a consequence, it did not query the prepended new registry first, but rather started with querying docker.io. The '--registry-prepend' option has been renamed to '--registry-add' and its behavior has been changed to query the registries added in the given order, with docker.io queried last. (BZ#1186153)

All docker users are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

run tests inside a docker repo allow unitfile to use /etc/sysconfig/docker-network Security fix for CVE-2014-9357, CVE-2014-9358, CVE-2014-9356

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Oracle Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2014-3110 advisory.

    [1.3.3-1.0.1]
    - Rename requirement of docker-io-pkg-devel in %package devel as docker-pkg-devel
    - Restore SysV init scripts for Oracle Linux 6
    - Require Oracle Unbreakable Enterprise Kernel Release 3 or higher
    - Rename as docker.
    - Re-enable btrfs graphdriver support

    [1.3.3-1]
    - Update source to 1.3.3 from https://github.com/docker/docker/releases/tag/v1.3.3       Path traversal during processing of absolute symlinks (CVE-2014-9356)       Escalation of privileges during decompression of LZMA (.xz) archives (CVE-2014-9357)

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

This docker version update fixes the following security and non security issues and adds additional features.

  - Updated to 1.4.0 (2014-12-11) :

  - Notable Features since 1.3.0 :

  - Set key=value labels to the daemon (displayed in `docker     info`), applied with new `-label` daemon flag

  - Add support for `ENV` in Dockerfile of the form: `ENV     name=value name2=value2...`

  - New Overlayfs Storage Driver

  - `docker info` now returns an `ID` and `Name` field

  - Filter events by event name, container, or image

  - `docker cp` now supports copying from container volumes

  - Fixed `docker tag`, so it honors `--force` when     overriding a tag for existing image.

  - Changes introduced by 1.3.3 (2014-12-11) :

  - Security :

  - Fix path traversal vulnerability in processing of     absolute symbolic links (CVE-2014-9356) - (bnc#909709)

  - Fix decompression of xz image archives, preventing     privilege escalation (CVE-2014-9357) - (bnc#909710)

  - Validate image IDs (CVE-2014-9358) - (bnc#909712)

  - Runtime :

  - Fix an issue when image archives are being read slowly

  - Client :

  - Fix a regression related to stdin redirection

  - Fix a regression with `docker cp` when destination is     the current directory

Security fix for CVE-2014-9357, CVE-2014-9358, CVE-2014-9356 Revert to using upstream v1.3.2 release Resolves: rhbz#1169035, rhbz#1169151

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Path traversal attacks are possible in the processing of absolute symlinks. In checking symlinks for traversals, only relative links were considered. This allowed path traversals to exist where they should have otherwise been prevented. This was exploitable via both archive extraction and through volume mounts. This vulnerability allowed malicious images or builds from malicious Dockerfiles to write files to the host system and escape containerization, leading to privilege escalation. (CVE-2014-9356)

It has been discovered that the introduction of chroot for archive extraction in Docker 1.3.2 had introduced a privilege escalation vulnerability. Malicious images or builds from malicious Dockerfiles could escalate privileges and execute arbitrary code as a root user on the Docker host by providing a malicious 'xz' binary. (CVE-2014-9357)

It has been discovered that Docker does not sufficiently validate Image IDs as provided either via 'docker load' or through registry communications. This allows for path traversal attacks, causing graph corruption and manipulation by malicious images, as well as repository spoofing attacks. (CVE-2014-9358)

ID	Name	Product	Family	Severity
83667	SUSE SLES12 Security Update : docker (SUSE-SU-2015:0082-1)	Nessus	SuSE Local Security Checks	high
81640	RHEL 7 : docker (RHSA-2015:0623)	Nessus	Red Hat Local Security Checks	high
80981	Fedora 20 : docker-io-1.4.1-6.fc20 (2015-1128)	Nessus	Fedora Local Security Checks	critical
80329	Oracle Linux 6 / 7 : docker (ELSA-2014-3110)	Nessus	Oracle Linux Local Security Checks	high
80278	openSUSE Security Update : docker (openSUSE-SU-2014:1722-1)	Nessus	SuSE Local Security Checks	high
79954	Fedora 21 : docker-io-1.4.0-1.fc21 (2014-16839)	Nessus	Fedora Local Security Checks	critical
79875	Amazon Linux AMI : docker (ALAS-2014-461)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2014-9357

critical

Tenable Plugins

high

high

critical

high

high

critical

high