Описание
Security update for runc
This update for runc fixes the following issues:
Security vulnerablities addressed:
- CVE-2019-5736: Effectively copying /proc/self/exe during re-exec to avoid write attacks to the host runc binary, which could lead to a container breakout (bsc#1121967)
- CVE-2018-16873: Fix a remote command execution during 'go get -u' (boo#1118897)
- CVE-2018-16874: Fix a directory traversal in 'go get' via curly braces in import paths (boo#1118898)
- CVE-2018-16875: Fix a CPU denial of service issue (boo#1118899)
Other changes and bug fixes:
- Update go requirements to >= go1.10
- Create a symlink in /usr/bin/runc to enable rootless Podman and Buildah.
- Make use of %license macro
- Remove 'go test' from %check section, as it has only ever caused us problems and hasn't (as far as I remember) ever caught a release-blocking issue. Smoke testing has been far more useful. (boo#1095817)
- Upgrade to runc v1.0.0~rc6. Upstream changelog is available from https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc6
Список пакетов
openSUSE Leap 15.0
Ссылки
- E-Mail link for openSUSE-SU-2019:0208-1
- SUSE Security Ratings
- SUSE Bug 1095817
- SUSE Bug 1118897
- SUSE Bug 1118898
- SUSE Bug 1118899
- SUSE Bug 1121967
- SUSE CVE CVE-2018-16873 page
- SUSE CVE CVE-2018-16874 page
- SUSE CVE CVE-2018-16875 page
- SUSE CVE CVE-2019-5736 page
Описание
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u".
Затронутые продукты
Ссылки
- CVE-2018-16873
- SUSE Bug 1118897
- SUSE Bug 1118898
- SUSE Bug 1118899
Описание
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). The attacker can cause an arbitrary filesystem write, which can lead to code execution.
Затронутые продукты
Ссылки
- CVE-2018-16874
- SUSE Bug 1118897
- SUSE Bug 1118898
- SUSE Bug 1118899
Описание
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
Затронутые продукты
Ссылки
- CVE-2018-16875
- SUSE Bug 1118897
- SUSE Bug 1118898
- SUSE Bug 1118899
Описание
runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.
Затронутые продукты
Ссылки
- CVE-2019-5736
- SUSE Bug 1121967
- SUSE Bug 1122185
- SUSE Bug 1173421
- SUSE Bug 1218894