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.
Advisories
Source ID Title
EUVD EUVD EUVD-2021-2523 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.
Github GHSA Github GHSA GHSA-gp4j-w3vj-7299 Information Exposure in RunC
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-06T03:07:31.309Z

Reserved: 2016-12-15T00:00:00

Link: CVE-2016-9962

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2017-01-31T22:59:01.783

Modified: 2025-04-20T01:37:25.860

Link: CVE-2016-9962

cve-icon Redhat

Severity : Important

Publid Date: 2017-01-11T00:00:00Z

Links: CVE-2016-9962 - Bugzilla

cve-icon OpenCVE Enrichment

No data.