FlawAtlas
Search the atlas
CVE-2016-9962 Moderate

CVE-2016-9962

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.

Exploit probability 0.4%
Published January 31, 2017
Required by Not available
Last source change July 8, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

46 explicit affected versions

Go github.com/opencontainers/runc
Go github.com/opencontainers/runc

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2016-9962

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.

View original source
Open Source Vulnerabilities GO-2022-0835

Information Exposure in RunC in github.com/opencontainers/runc

View original source
Open Source Vulnerabilities GHSA-gp4j-w3vj-7299

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.

View original source

05 / REFERENCES

Further evidence