ID CVE-2014-9357
Summary 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.
References
Vulnerable Configurations
  • Docker 1.3.2
    cpe:2.3:a:docker:docker:1.3.2
CVSS
Base: 10.0 (as of 30-12-2014 - 13:24)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2014-820.NASL
    description 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
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 80278
    published 2014-12-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80278
    title openSUSE Security Update : docker (openSUSE-SU-2014:1722-1)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2015-1128.NASL
    description 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.
    last seen 2019-02-21
    modified 2015-10-19
    plugin id 80981
    published 2015-01-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80981
    title Fedora 20 : docker-io-1.4.1-6.fc20 (2015-1128)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2015-0082-1.NASL
    description 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.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 83667
    published 2015-05-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=83667
    title SUSE SLES12 Security Update : docker (SUSE-SU-2015:0082-1)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2014-3110.NASL
    description Description of changes: [1.3.3-1.0.1] - Add symlink/LICENSE.BSD and symlink/LICENSE.APACHE under %files macro for docker-pkg-devel - Rename requirement of docker-io-pkg-devel in %package devel as docker-pkg-devel - Rename as docker - Restore SysV init scripts for Oracle Linux 6 [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) Path traversal and spoofing opportunities presented through image identifiers (CVE-2014-9358)
    last seen 2019-02-21
    modified 2015-12-01
    plugin id 80329
    published 2015-01-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=80329
    title Oracle Linux 6 / 7 : docker (ELSA-2014-3110)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2014-461.NASL
    description 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)
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 79875
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79875
    title Amazon Linux AMI : docker (ALAS-2014-461)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-16839.NASL
    description 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.
    last seen 2019-02-21
    modified 2015-10-19
    plugin id 79954
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79954
    title Fedora 21 : docker-io-1.4.0-1.fc21 (2014-16839)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2015-0623.NASL
    description 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.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 81640
    published 2015-03-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=81640
    title RHEL 7 : docker (RHSA-2015:0623)
refmap via4
bugtraq 20141212 Docker 1.3.3 - Security Advisory [11 Dec 2014]
confirm https://groups.google.com/forum/#!msg/docker-user/nFAz-B-n4Bw/0wr3wvLsnUwJ
Last major update 30-12-2014 - 14:33
Published 16-12-2014 - 13:59
Last modified 09-10-2018 - 15:55
Back to Top