Withdrawn by the publisher.

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.

Affected: Go: github.com/opencontainers/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.

containerd-1.4.8-2.2 on GA media

docker: insecure opening of file-descriptor allows privilege escalation

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

Affected: Ubuntu:16.04:LTS: docker.io, Ubuntu:18.04:LTS: 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.

Ein lokaler Angreifer kann eine Schwachstelle in docker ausnutzen, um seine Privilegien zu erhöhen.