RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.

V1.0 final release

----

bump runc commit

----

Update to latest release candidate

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

  - containerd,

  - docker to version 1.12.6 and

  - runc fixes several issues.

This security issues was fixed :

  - CVE-2016-9962: container escape vulnerability     (bsc#1012568).

Thsese non-security issues were fixed :

  - boo#1019251: Add a delay when starting docker service 

  - Fixed bash-completion

  - boo#1015661: add the /usr/bin/docker-run symlink 

For additional details please see the changelog.

Fix CVE-2016-9962 - Insecure opening of file-descriptor allows privilege escalation

----

built docker @projectatomic/docker-1.12 commit 6009905

----

built docker @projectatomic/docker-1.12 commit 97974ae

----

built docker @projectatomic/docker-1.12 commit 7b5044b

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.

Resolves: #1412238 - *CVE-2016-9962* - set init processes as non-dumpable,

----

patch to enable seccomp

----

bump to 1.0.0 rc2

----

Resolves: #1342707 - bump to v1.0.0-rc1

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.

An update for runc 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.

The runC tool is a lightweight, portable implementation of the Open Container Format (OCF) that provides container runtime.

Security Fix(es) :

* The runc component used by `docker exec` feature of docker allowed additional container processes via to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain low-level access to these new processes during initialization. An attacker can, depending on the nature of the incoming process, leverage this to elevate access to the host. This ranges from accessing host content through the file descriptors of the incoming process to, potentially, a complete container escape by leveraging memory access or syscall interception. (CVE-2016-9962)

Red Hat would like to thank the Docker project for reporting this issue. Upstream acknowledges Aleksa Sarai (SUSE) and Tonis Tiigi (Docker) as the original reporters.

An update for docker-latest 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, and self-sufficient container that will run virtually anywhere.

The following packages have been upgraded to a newer upstream version:
docker-latest (1.12.5). (BZ#1404309)

Security Fix(es) :

* The runc component used by `docker exec` feature of docker allowed additional container processes via to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain low-level access to these new processes during initialization. An attacker can, depending on the nature of the incoming process, leverage this to elevate access to the host. This ranges from accessing host content through the file descriptors of the incoming process to, potentially, a complete container escape by leveraging memory access or syscall interception. (CVE-2016-9962)

Red Hat would like to thank the Docker project for reporting this issue. Upstream acknowledges Aleksa Sarai (SUSE) and Tonis Tiigi (Docker) as the original reporters.

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.

The following packages have been upgraded to a newer upstream version:
docker (1.12.5). (BZ#1404298)

Security Fix(es) :

* The runc component used by `docker exec` feature of docker allowed additional container processes via to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain low-level access to these new processes during initialization. An attacker can, depending on the nature of the incoming process, leverage this to elevate access to the host. This ranges from accessing host content through the file descriptors of the incoming process to, potentially, a complete container escape by leveraging memory access or syscall interception. (CVE-2016-9962)

Red Hat would like to thank the Docker project for reporting this issue. Upstream acknowledges Aleksa Sarai (SUSE) and Tonis Tiigi (Docker) as the original reporters.

Bug Fix(es) :

* The docker containers and images did not read proxy variables from the environment when contacting registries. As a consequence, a user could not pull image when the system was configured to use a proxy.
The containers and images have been fixed to read proxy variables from the environment, and pulling images now from a system with a proxy works correctly. (BZ# 1393816)

* Occasionally the docker-storage-setup service could start before a thin pool is ready which caused it to failed. As a consequence, the docker daemon also failed. This bug has been fixed and now docker-storage-setup waits for a thin pool to be created for 60 seconds. This default time can be configured. As a result, docker and docker-storage-setup start correctly upon reboot. (BZ#1316786)

* Previously, the docker daemon's unit file was not supplying the userspace proxy path. As a consequence, containers that exposed ports could not be started. To fix this bug, the unit file was updated to include the userspace proxy path option to the daemon start command, along with several other minor packaging fixes. As a result, containers that expose ports can now be started as expected.
(BZ#1406460)

* Previously, the system CA (Certificate Authority) pool was excluded when the registry CA is used from the /etc/docker/certs.d/ directory.
As a consequence, pulling images failed with the following error :

Failed to push image: x509: certificate signed by unknown authority

This bug has been fixed and docker now reads the system CA pool correctly and pulling images now work correctly. (BZ#1400372)

* Previously, the docker daemon option did not handle correctly the '--block-registry docker.io' option. As a consequence, docker allowed pulling images from docker.io even when the '--block-registry docker.io' option was enabled. This update fixed the handling of the option, and now using '--block-registry docker.io' correctly blocks image pulling. (BZ# 1395401)

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

  - RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container.
    This allows the main processes of the container, if running as root, to gain access to file-descriptors of     these new processes during the initialization and can lead to container escapes or modification of runC     state before the process is fully placed inside the container. (CVE-2016-9962)

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

The remote host is affected by the vulnerability described in GLSA-201701-34 (runC: Privilege escalation)

    A vulnerability was discovered in runC that allows additional container       processes via &lsquo;runc exec&rsquo; to be ptraced by the pid 1 of the       container.  This allows the main processes of the container, if running       as root, to gain access to file-descriptors of these new processes.
  Impact :

    An attacker, who is able to successfully escape the container or modify       runC&rsquo;s state before process initialization, could escalate privileges.
  Workaround :

    There is no known workaround at this time.

Fix [CVE-2016-9962] Insecure opening of file-descriptor allows privilege Fix BZ#1412148 - containerd: container did not start before the specified timeout

----

use container-selinux >= 2:2.0-2

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.

It was discovered that runC allowed additional container processes via `runc exec` to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file descriptors of these new processes during the initialization, which can lead to container escapes or modification of runC state before the process is fully placed inside the container.

ID	Name	Product	Family	Severity
102086	Fedora 25 : 1:runc (2017-20cdb2063a)	Nessus	Fedora Local Security Checks	medium
96918	openSUSE Security Update : containerd / docker / runc (openSUSE-2017-181)	Nessus	SuSE Local Security Checks	medium
96678	Fedora 24 : 2:docker-latest (2017-c2c2d1be16)	Nessus	Fedora Local Security Checks	medium
96616	Fedora 25 : 1:runc (2017-0200646669)	Nessus	Fedora Local Security Checks	medium
96598	RHEL 7 : runc (RHSA-2017:0127)	Nessus	Red Hat Local Security Checks	medium
96597	RHEL 7 : docker-latest (RHSA-2017:0123)	Nessus	Red Hat Local Security Checks	medium
96596	RHEL 7 : docker (RHSA-2017:0116)	Nessus	Red Hat Local Security Checks	medium
96589	Oracle Linux 6 / 7 : docker-engine / docker-engine-selinux (ELSA-2017-3511)	Nessus	Oracle Linux Local Security Checks	high
96509	Fedora 25 : 2:docker-latest (2017-fcd02e2c2d)	Nessus	Fedora Local Security Checks	medium
96475	GLSA-201701-34 : runC: Privilege escalation	Nessus	Gentoo Local Security Checks	medium
96469	Fedora 25 : 2:docker (2017-dbc2b618eb)	Nessus	Fedora Local Security Checks	medium
96394	Amazon Linux AMI : docker (ALAS-2017-783)	Nessus	Amazon Linux Local Security Checks	medium

Detections

Analytics

CVE-2016-9962

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

high

medium

medium

medium

medium