ALT-BU-2019-3445-1
Branch sisyphus update bulletin.
Closed vulnerabilities
BDU:2019-02448
Уязвимость менеджера для серверов Cockpit, вызванная выходом операции за границы буфера в памяти, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2019-3804
It was found that cockpit before version 184 used glib's base64 decode functionality incorrectly resulting in a denial of service attack. An unauthenticated attacker could send a specially crafted request with an invalid base64-encoded cookie which could cause the web service to crash.
- RHSA-2019:1569
- RHSA-2019:1569
- RHSA-2019:1571
- RHSA-2019:1571
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3804
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3804
- https://github.com/cockpit-project/cockpit/commit/c51f6177576d7e12
- https://github.com/cockpit-project/cockpit/commit/c51f6177576d7e12
- https://github.com/cockpit-project/cockpit/pull/10819
- https://github.com/cockpit-project/cockpit/pull/10819
Package kubernetes updated to version 1.13.2-alt1 for branch sisyphus in task 219598.
Closed vulnerabilities
BDU:2020-00025
Уязвимость библиотеки синтаксического анализатора YAML программного средства управления кластерами виртуальных машин Kubernetes, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2019-11243
In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig()
Modified: 2024-11-21
CVE-2019-11253
Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.
- RHSA-2019:3239
- RHSA-2019:3239
- RHSA-2019:3811
- RHSA-2019:3811
- RHSA-2019:3905
- RHSA-2019:3905
- https://github.com/kubernetes/kubernetes/issues/83253
- https://github.com/kubernetes/kubernetes/issues/83253
- CVE-2019-11253: denial of service vulnerability from malicious YAML or JSON payloads
- CVE-2019-11253: denial of service vulnerability from malicious YAML or JSON payloads
- https://security.netapp.com/advisory/ntap-20191031-0006/
- https://security.netapp.com/advisory/ntap-20191031-0006/
Package purple-telegram updated to version 1.3.1-alt1 for branch sisyphus in task 219605.
Closed bugs
Please update
Package firefox-esr updated to version 60.4.0-alt2 for branch sisyphus in task 219148.
Closed bugs
Перестал собираться firefox-esr
Closed vulnerabilities
BDU:2020-01887
Уязвимость реализации команды «go get» языка программирования Go, позволяющая нарушителю выполнить произвольный код
BDU:2020-01888
Уязвимость реализации команды «go get» языка программирования Go, позволяющая нарушителю выполнить произвольный код
BDU:2020-01889
Уязвимость пакета crypto/x509 языка программирования Go, позволяющая нарушителю вызвать отказ в обслуживании
Modified: 2024-11-21
CVE-2018-16873
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".
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1703
- openSUSE-SU-2019:1703
- openSUSE-SU-2020:0554
- openSUSE-SU-2020:0554
- 106226
- 106226
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16873
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16873
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2591-1] golang-1.7 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2591-1] golang-1.7 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2592-1] golang-1.8 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2592-1] golang-1.8 security update
- GLSA-201812-09
- GLSA-201812-09
Modified: 2024-11-21
CVE-2018-16874
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.
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1703
- openSUSE-SU-2019:1703
- openSUSE-SU-2020:0554
- openSUSE-SU-2020:0554
- 106228
- 106228
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16874
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16874
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2591-1] golang-1.7 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2591-1] golang-1.7 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2592-1] golang-1.8 security update
- [debian-lts-announce] 20210313 [SECURITY] [DLA 2592-1] golang-1.8 security update
- GLSA-201812-09
- GLSA-201812-09
Modified: 2024-11-21
CVE-2018-16875
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.
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1079
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1444
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1499
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1506
- openSUSE-SU-2019:1703
- openSUSE-SU-2019:1703
- 106230
- 106230
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16875
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16875
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- https://groups.google.com/forum/?pli=1#%21topic/golang-announce/Kw31K8G7Fi0
- GLSA-201812-09
- GLSA-201812-09