docker: insecure opening of file-descriptor allows privilege escalation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 Extras | |||
| docker-2:1.12.5-14.el7 | cpe:/a:redhat:rhel_extras_other:7 | RHSA-2017:0116 | 2017-01-17T00:00:00Z |
| docker-latest-0:1.12.5-14.el7 | cpe:/a:redhat:rhel_extras_other:7 | RHSA-2017:0123 | 2017-01-17T00:00:00Z |
| runc-0:1.0.0-1.rc2.el7 | cpe:/a:redhat:rhel_extras_other:7 | RHSA-2017:0127 | 2017-01-17T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
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 |
GHSA-gp4j-w3vj-7299 | Information Exposure in RunC |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.412% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.