Critcial security vulnerabilties in docker < 1.3.3
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| docker.io (Ubuntu) |
Fix Released
|
High
|
James Page | ||
| Trusty |
Fix Released
|
High
|
Unassigned | ||
| Utopic |
Won't Fix
|
High
|
Unassigned | ||
| Vivid |
Fix Released
|
High
|
James Page | ||
Bug Description
Today, we are releasing Docker 1.3.2 in order to address two critical
security issues. This release also includes several bugfixes, including
changes to the insecure-registry option. Below are CVE descriptions for the
vulnerabilities addressed in this release.
Docker 1.3.2 is available immediately for all supported platforms:
https:/
Docker Security Advisory [24 Nov 2014]
=======
=======
[CVE-2014-6407] Archive extraction allowing host privilege escalation
=======
Severity: Critical
Affects: Docker up to 1.3.1
The Docker engine, up to and including version 1.3.1, was vulnerable to
extracting files to arbitrary paths on the host during ‘docker pull’ and
‘docker load’ operations. This was caused by symlink and hardlink
traversals present in Docker's image extraction. This vulnerability could
be leveraged to perform remote code execution and privilege escalation.
Docker 1.3.2 remedies this vulnerability. Additional checks have been added
to pkg/archive and image extraction is now performed in a chroot. No
remediation is available for older versions of Docker and users are advised
to upgrade.
Related vulnerabilities discovered by Florian Weimer of Red Hat Product
Security and independent researcher, Tõnis Tiigi.
=======
[CVE-2014-6408] Security options applied to image could lead to container
escalation
=======
Severity: Critical
Affects: Docker 1.3.0-1.3.1
Docker versions 1.3.0 through 1.3.1 allowed security options to be applied
to images, allowing images to modify the default run profile of containers
executing these images. This vulnerability could allow a malicious image
creator to loosen the restrictions applied to a container’s processes,
potentially facilitating a break-out.
Docker 1.3.2 remedies this vulnerability. Security options applied to
images are no longer consumed by the Docker engine and will be ignored.
Users are advised to upgrade.
=======
Other changes:
=======
Besides the above CVEs, the 1.3.2 release allows administrators to pass a
CIDR-formatted range of addresses for '—insecure-
allowing a cleartext registry to exist on localhost is now default
behavior. This change was made due to user feedback following the changes
made in 1.3.1 to resolve CVE-2014-5277.
---
Docker 1.3.3 has been released to address several vulnerabilities and is immediately available for all supported platforms: https:/
This release addresses vulnerabilities which could be exploited by a malicious Dockerfile, image, or registry to compromise a Docker host, modify images, or spoof official repository images. Note that today we also expect to see the release of Docker 1.4.0, also containing these fixes. While version 1.3.3 is a security-focused update, Docker 1.4.0 will include over 180 new commits, primarily bug fixes.
It is highly recommended that users upgrade to Docker Engine 1.3.3 or higher.
Please send any questions to <email address hidden>.
Docker Security Advisory [141211]
-------
=======
[CVE-2014-9356] Path traversal during processing of absolute symlinks
=======
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.
We are releasing Docker 1.3.3 to address this vulnerability. Users are highly encouraged to upgrade.
Discovered by Tõnis Tiigi.
=======
[CVE-2014-9357] Escalation of privileges during decompression of LZMA (.xz) archives
=======
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 privileged root user on the Docker host by providing a malicious ‘xz’ binary.
We are releasing Docker 1.3.3 to address this vulnerability. Only Docker 1.3.2 is vulnerable. Users are highly encouraged to upgrade.
Discovered by Tõnis Tiigi.
=======
[CVE-2014-9358] Path traversal and spoofing opportunities presented through image identifiers
=======
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.
We are releasing Docker 1.3.3 to address this vulnerability. Users are highly encouraged to upgrade.
Discovered by Eric Windisch of Docker, Inc.
| information type: | Public → Public Security |
| Changed in docker.io (Ubuntu): | |
| importance: | Undecided → High |
| Changed in docker.io (Ubuntu Vivid): | |
| status: | New → Fix Committed |
| Changed in docker.io (Ubuntu Utopic): | |
| importance: | Undecided → High |
| Changed in docker.io (Ubuntu Trusty): | |
| importance: | Undecided → High |
| James Page (james-page) wrote | #1 |
| Changed in docker.io (Ubuntu Vivid): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in docker.io (Ubuntu Trusty): | |
| status: | New → Confirmed |
| Changed in docker.io (Ubuntu Utopic): | |
| status: | New → Confirmed |
| summary: |
- Critcial security vulnerabilties in docker < 1.3.2 + Critcial security vulnerabilties in docker < 1.3.3 |
| description: | updated |
| Changed in docker.io (Ubuntu Vivid): | |
| status: | Fix Released → Confirmed |
| James Page (james-page) wrote | #4 |
| Changed in docker.io (Ubuntu Vivid): | |
| assignee: | nobody → James Page (james-page) |
| status: | Confirmed → In Progress |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in docker.io (Ubuntu Vivid): | |
| status: | In Progress → Fix Released |
| James Page (james-page) wrote | #6 |
| James Page (james-page) wrote | #7 |
| Tyler Hicks (tyhicks) wrote | #8 |
| Dustin Kirkland (kirkland) wrote Re: [Bug 1396572] Re: Critcial security vulnerabilties in docker < 1.3.3 | #9 |
| James Page (james-page) wrote | #10 |
| Dustin Kirkland (kirkland) wrote | #11 |
| Steve Beattie (sbeattie) wrote | #12 |
| Launchpad Janitor (janitor) wrote | #13 |
| Changed in docker.io (Ubuntu Trusty): | |
| status: | Confirmed → Fix Released |
| Rolf Leggewie (r0lf) wrote | #14 |
| Changed in docker.io (Ubuntu Utopic): | |
| status: | Confirmed → Won't Fix |
1.3.2 packages for 14.04 and 14.10 will end up here first:
https:/
This security bug needs discussion in the context of the email to the TB last month with regards to backporting of newer docker releases to the LTS release.