libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the password file in a container.

According to the version of the docker packages installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - 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.(CVE-2016-3697)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-201612-28 (Docker: Privilege escalation)

    Docker does not properly distinguish between numeric UIDs and string       usernames.
  Impact :

    Local attackers could possibly escalate their privileges.
  Workaround :

    There is no known workaround at this time.

An update for docker is now available for Red Hat Enterprise Linux 7 Extras.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Docker is an open source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.

Security Fix(es) :

* 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. (CVE-2016-3697)

This issue was discovered by Mrunal Patel (Red Hat).

Bug Fix(es) :

* This update also provides various bug fixes and enhancements. Users are advised to upgrade to these updated packages.

Resolves: #1340519 - add TasksMax=infinity

----

built docker @projectatomic/fedora-1.10.3 commit f476348

----

built docker @projectatomic/fedora-1.10.3 commit f476348

----

built docker @projectatomic/fedora-1.10.3 commit 4158ccc

----

Resolves: #1335649 - enable Red Hat subscription use in Docker containers on Fedora

----

built docker @projectatomic/fedora-1.10.3 commit 8ecd47f

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

built docker @projectatomic/fedora-1.10.3 commit f476348

----

built docker @projectatomic/fedora-1.10.3 commit f476348

----

built docker @projectatomic/fedora-1.10.3 commit 4158ccc

----

Resolves: #1335649 - enable Red Hat subscription use in Docker containers on Fedora

----

built docker @projectatomic/fedora-1.10.3 commit 8ecd47f

----

built docker @projectatomic/fedora-1.10.3 commit 8ecd47f

----

built docker @projectatomic/fedora-1.10.3 commit 667d6d1

----

built docker @projectatomic/fedora-1.10.3 commit bba2d6d

----

built docker @projectatomic/fedora-1.10.3 commit a41254f

----

built docker @projectatomic/fedora-1.10.3 commit#964eda6

----

built docker @projectatomic/fedora-1.10.3 commit#ef2fa35

----

docker package runtime depends on docker-forward-journald

----

rebuilt to remove dockerroot user creation

----

rebuilt to remove dockerroot user creation

----

rebuilt to include dss_libdir directory

----

built docker @projectatomic/fedora-1.10.2 commit#86e59a5

----

rebuilt with seccomp enabled

----

built docker @projectatomic/fedora-1.10.1 commit#6c71d8f

----

built docker @projectatomic/fedora-1.10.1 commit#6c71d8f

----

rebuilt, no change

----

built docker @projectatomic/fedora-1.10.2 commit#0f5ac89

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for docker fixes the following issues :

Security issues fixed :

  - CVE-2016-3697: Potential privilege escalation via     confusion of usernames and UIDs (boo#976777)

Bugs fixed :

  - devicemapper: fix zero-sized field access

  - remove docker-netns-aarch64.patch: This patch was adding     We'll fix that later if we want to release for those     archs.

  - Exclude init scripts other than systemd from the     test-package make it explicit.

  - Add test subpackage and fix line numbers in patches

The remote Oracle Linux 6 / 7 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2016-3568 advisory.

    [1.10.3-1.0.3]
    - CVE-2016-3697: docker: Potential privilege escalation via confusion of usernames and UIDs [orabug     23279003]

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

An update for docker is now available for Red Hat Enterprise Linux 7 Extras.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Docker is an open source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.

Security Fix(es) :

* 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. (CVE-2016-3697)

This issue was discovered by Mrunal Patel (Red Hat).

Bug Fix(es) :

* The process of pulling an image spawns a new 'goroutine' for each layer in the image manifest. If any of these downloads, everything stops and an error is returned, even though other goroutines would still be running and writing output through a progress reader which is attached to an http response writer. Since the request handler had already returned from the first error, the http server panics when one of these download goroutines makes a write to the response writer buffer. This bug has been fixed, and docker no longer panics when pulling an image. (BZ#1264562)

* Previously, in certain situations, a container rootfs remained busy during container removal. This typically happened if a container mount point leaked into another mount namespace. As a consequence, container removal failed. To fix this bug, a new docker daemon option 'dm.use_deferred_deletion' has been provided. If set to true, this option will defer the container rootfs deletion. The user will see success on container removal but the actual thin device backing the rootfs will be deleted later when it is not busy anymore. (BZ#1190492)

* Previously, the Docker unit file had the 'Restart' option set to 'on-failure'. Consequently, the docker daemon was forced to restart even in cases where it couldn't be started because of configuration or other issues and this situation forced unnecessary restarts of the docker-storage-setup service in a loop. This also caused real error messages to be lost due to so many restarts. To fix this bug, 'Restart=on-failure' has been replaced with 'Restart=on-abnormal' in the docker unit file. As a result, the docker daemon will not automatically restart if it fails with an unclean exit code.
(BZ#1319783)

* Previously, the request body was incorrectly read twice by the docker daemon and consequently, an EOF error was returned. To fix this bug, the code which incorrectly read the request body the first time has been removed. As a result, the EOF error is no longer returned and the body is correctly read when really needed. (BZ#1329743)

Enhancement(s) :

* The /usr/bin/docker script now calls /usr/bin/docker-current or /usr/bin/ docker-latest based on the value of the sysconfig variable DOCKERBINARY present in /etc/sysconfig/docker. /usr/bin/docker and /etc/sysconfig/docker provided by the docker-common package allow the admin to configure which docker client binary gets called.
/usr/bin/docker will call /usr/bin/ docker-latest by default when docker is not installed. If docker is installed, /usr/bin/docker will call /usr/bin/docker-current by default, unless DOCKERBINARY is set to /usr/bin/docker-latest in /etc/sysconfig/ docker. This way, you can use docker-latest or docker without the need to check which version of the daemon is currently running. (BZ#1328219)

ID	Name	Product	Family	Severity
99779	EulerOS 2.0 SP1 : docker (EulerOS-SA-2016-1016)	Nessus	Huawei Local Security Checks	high
95696	GLSA-201612-28 : Docker: Privilege escalation	Nessus	Gentoo Local Security Checks	high
94606	RHEL 7 : docker (RHSA-2016:2634)	Nessus	Red Hat Local Security Checks	high
92108	Fedora 24 : 2:docker (2016-6ef52e1fc3)	Nessus	Fedora Local Security Checks	high
92105	Fedora 23 : 2:docker (2016-6a0d540088)	Nessus	Fedora Local Security Checks	high
91401	openSUSE Security Update : docker (openSUSE-2016-643)	Nessus	SuSE Local Security Checks	high
91294	Oracle Linux 6 / 7 : docker-engine (ELSA-2016-3568)	Nessus	Oracle Linux Local Security Checks	high
91115	RHEL 7 : docker (RHSA-2016:1034)	Nessus	Red Hat Local Security Checks	high

Detections

Analytics

CVE-2016-3697

high

Tenable Plugins

high

high

high

high

high

high

high

high