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.
First Last Prev Next    This bug is not in your last search results.
Bug 1329450 - (CVE-2016-3697) CVE-2016-3697 docker: privilege escalation via confusion of usernames and UIDs
CVE-2016-3697 docker: privilege escalation via confusion of usernames and UIDs
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=20160422,repor...
: Security
Depends On: 1329451 1329452 1329453 1329454 1329728
Blocks: 1391583
  Show dependency tree / graph
 
Reported: 2016-04-21 21:54 EDT by Trevor Jay
Modified: 2018-06-29 18:08 EDT (History)
22 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It was found that Docker would launch containers under the specified UID instead of a username. An attacker able to launch a container could use this flaw to escalate their privileges to root within the launched container.
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)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1034 normal SHIPPED_LIVE Moderate: docker security, bug fix, and enhancement update 2016-05-12 15:15:01 EDT
Red Hat Product Errata RHSA-2016:2634 normal SHIPPED_LIVE Moderate: docker security and bug fix update 2016-11-03 16:51:48 EDT

  None (edit)
Description Trevor Jay 2016-04-21 21:54:56 EDT 
Container launch does not distinguish between numeric UIDs and string usernames. A malicious image can provide a username to UID mapping at a high privileged level. This means that innoculous looking launches such as:

    docker -u 1000 ...

actually result in the image processes running as root.

This ambiguity also confuses OpenShift's UID-based controls.
Comment 1 Trevor Jay 2016-04-21 22:00:48 EDT 
Acknowledgments:

Name: Mrunal Patel (Red Hat)
Comment 4 Trevor Jay 2016-04-21 22:03:38 EDT 
Created docker tracking bugs for this issue:

Affects: fedora-all [bug 1329454]
Comment 5 errata-xmlrpc 2016-05-12 11:17:58 EDT 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extras

Via RHSA-2016:1034 https://rhn.redhat.com/errata/RHSA-2016-1034.html
Comment 6 errata-xmlrpc 2016-11-04 05:07:25 EDT 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extras

Via RHSA-2016:2634 https://rhn.redhat.com/errata/RHSA-2016-2634.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.