Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1219058 - (CVE-2015-3629) CVE-2015-3629 docker: symlink traversal on container respawn allows local privilege escalation
CVE-2015-3629 docker: symlink traversal on container respawn allows local pri...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20150507,repor...
: Security
Depends On: 1219701 1219702 1219703 1219704
Blocks: 1219067
  Show dependency treegraph
 
Reported: 2015-05-06 09:58 EDT by Martin Prpič
Modified: 2015-11-25 05:32 EST (History)
17 users (show)

See Also:
Fixed In Version: docker 1.6.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Prpič 2015-05-06 09:58:55 EDT
The following flaw was reported in Docker:

Libcontainer version 1.6.0 introduced changes which facilitated a mount namespace breakout upon respawn of a container. This allowed malicious images to write files to the host system and escape containerization.

Libcontainer and Docker Engine 1.6.1 address this vulnerability.

Acknowledgements:

Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue.
Comment 1 Trevor Jay 2015-05-07 21:33:37 EDT
This issue is exploitable by malicious Docker images. Red Hat supports images from it's own registry, ISV images certified by the Red Hat certification program, and images using qualified customer content.
Comment 3 Trevor Jay 2015-05-07 21:45:21 EDT
Created docker-io tracking bugs for this issue:

Affects: fedora-all [bug 1219703]
Affects: epel-6 [bug 1219704]

Note You need to log in before you can comment on or make changes to this bug.