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.

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.

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.

RunC allowed additional container processes via 'runc exec' to be ptra ...

Security update for containerd, docker, runc

Security update for containerd, docker, runc

ELSA-2017-3511: docker-engine docker-engine-selinux security and bugfix update (IMPORTANT)

Уязвимость инструмента для запуска изолированных контейнеров Runc, связанная с одновременным выполнением с использованием общего ресурса с неправильной синхронизацией, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании

Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork, runc

Security update for docker-stable

Security update for docker-stable