Information Exposure in RunC
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-9962US | medium6.4 | — | ||
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 ga… | ||||
02
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2017-0116.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2017-0123.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2017-0127.htmlWEB
- http://seclists.org/fulldisclosure/2017/Jan/21WEB
- http://seclists.org/fulldisclosure/2017/Jan/29WEB
- http://www.securityfocus.com/archive/1/540001/100/0/threadedWEB
- http://www.securityfocus.com/bid/95361WEB
- https://access.redhat.com/security/vulnerabilities/cve-2016-9962WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan