Important: container-tools:rhel8 security and bug fix update

ELSA-2019-4269: container-tools:ol8 security and bug fix update (IMPORTANT)

runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory.

runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory.

runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory.

runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other ...

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

Security update for docker-runc

Security update for docker-runc

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

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

Security update for runc

Security update for docker-runc

Security update for docker-runc

Incorrect Authorization in runc

Уязвимость компонента AppArmor инструмента для запуска изолированных контейнеров runc, связанная с недостатками механизма авторизации, позволяющая нарушителю монтировать вредоносный образ Docker в каталог /proc

An issue was discovered in Podman in libpod before 1.6.0. It resolves a symlink in the host context during a copy operation from the container to the host, because an undesired glob operation occurs. An attacker could create a container image containing particular symlinks that, when copied by a victim user to the host filesystem, may overwrite existing files with others from the host.

An issue was discovered in Podman in libpod before 1.6.0. It resolves a symlink in the host context during a copy operation from the container to the host, because an undesired glob operation occurs. An attacker could create a container image containing particular symlinks that, when copied by a victim user to the host filesystem, may overwrite existing files with others from the host.

An issue was discovered in Podman in libpod before 1.6.0. It resolves ...