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 1219065 - (CVE-2015-3631) CVE-2015-3631 docker: volume mounts allow LSM profile escalation
CVE-2015-3631 docker: volume mounts allow LSM profile escalation
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: 1219713 1219714 1219715 1219716
Blocks: 1219067
  Show dependency treegraph
 
Reported: 2015-05-06 10:05 EDT by Martin Prpič
Modified: 2016-01-21 07:19 EST (History)
18 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 10:05:08 EDT
The following flaw was reported in Docker:

By allowing volumes to override files of /proc within a mount namespace, a user could specify arbitrary policies for Linux Security Modules, including setting an unconfined policy underneath AppArmor, or a docker_t policy for processes managed by SELinux. In all versions of Docker up until 1.6.1, it is possible for malicious images to configure volume mounts such that files of proc may be overridden.

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:42 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:50:13 EDT
Created docker-io tracking bugs for this issue:

Affects: fedora-all [bug 1219715]
Affects: epel-6 [bug 1219716]

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