diff --git a/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-04.xml b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-04.xml new file mode 100644 index 0000000000..0ca2ad31f7 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-04.xml @@ -0,0 +1,60 @@ + + + + cURL: Certificate validation error + A coding error has been found in cURL, causing the TLS Certificate + Status Request extension check to always return true. + + curl + 2017-03-28 + 2017-03-28: 1 + 610572 + remote + + + 7.53.0 + 7.53.0 + + + +

cURL is a tool and libcurl is a library for transferring data with URL + syntax. +

+
+ +

cURL and applications linked against libcurl support “OCSP + stapling”, also known as the TLS Certificate Status Request extension + (using the CURLOPT_SSL_VERIFYSTATUS option). When telling cURL to use + this feature, it uses that TLS extension to ask for a fresh proof of the + server’s certificate’s validity. If the server doesn’t support the + extension, or fails to provide said proof, cURL is expected to return an + error. + Due to a coding mistake, the code that checks for a test success or + failure, ends up always thinking there’s valid proof, even when there + is none or if the server doesn’t support the TLS extension in question. +

+
+ +

Due to the error, a user maybe does not detect when a server’s + certificate goes invalid or otherwise be mislead that the server is in a + better shape than it is in reality. +

+
+ +

There is no known workaround at this time.

+
+ +

All cURL users should upgrade to the latest version:

+ + + # emerge --sync + # emerge --ask --oneshot --verbose ">=net-misc/curl-7.53.0" + + +
+ + CVE-2017-2629 + + BlueKnight + whissi +
diff --git a/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-05.xml b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-05.xml new file mode 100644 index 0000000000..27d2040bb1 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-05.xml @@ -0,0 +1,51 @@ + + + + GNU Libtasn1: Denial of Service + A vulnerability in Libtasn1 allows remote attackers to cause a + Denial of Service condition. + + libtasn1 + 2017-03-28 + 2017-03-28: 1 + 579748 + remote + + + 4.8 + 4.8 + + + +

A library that provides Abstract Syntax Notation One (ASN.1, as + specified by the X.680 ITU-T recommendation) parsing and structures + management, and Distinguished Encoding Rules (DER, as per X.690) encoding + and decoding functions. +

+
+ +

Libtasn1 does not correctly handle certain malformed DER certificates.

+
+ +

A remote attacker could entice a user or automated system to process a + specially crafted certificate using Libtasn1, resulting in a Denial of + Service condition. +

+
+ +

There is no known workaround at this time.

+
+ +

All Libtasn1 users should upgrade to the latest version:

+ + + # emerge --sync + # emerge --ask --oneshot --verbose ">=dev-libs/libtasn1-4.8" + +
+ + CVE-2016-4008 + + b-man + whissi +
diff --git a/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-06.xml b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-06.xml new file mode 100644 index 0000000000..8459b1341e --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-06.xml @@ -0,0 +1,49 @@ + + + + Deluge: Remote execution of arbitrary code + A vulnerability in Deluge might allow remote attackers to execute + arbitrary code. + + deluge + 2017-03-28 + 2017-03-28: 1 + 612144 + remote + + + 1.3.14 + 1.3.14 + + + +

Deluge is a BitTorrent client.

+
+ +

A CSRF vulnerability was discovered in the web UI of Deluge.

+
+ +

A remote attacker could entice a user currently logged in into Deluge + web UI to visit a malicious web page which uses forged requests to make + Deluge download and install a Deluge plug-in provided by the attacker. + The plug-in can then execute arbitrary code as the user running Deluge. +

+
+ +

There is no known workaround at this time.

+
+ +

All Deluge users should upgrade to the latest version:

+ + + # emerge --sync + # emerge --ask --oneshot --verbose ">=net-p2p/deluge-1.3.14" + + +
+ + CVE-2017-7178 + + whissi + whissi +
diff --git a/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-07.xml b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-07.xml new file mode 100644 index 0000000000..de0af87a65 --- /dev/null +++ b/sdk_container/src/third_party/portage-stable/metadata/glsa/glsa-201703-07.xml @@ -0,0 +1,63 @@ + + + + Xen: Privilege Escalation + A vulnerability in Xen's bundled QEMU version might allow privilege + escalation. + + xen + 2017-03-28 + 2017-03-28: 1 + 609120 + local + + + 4.7.1-r8 + 4.7.1-r8 + + + +

Xen is a bare-metal hypervisor.

+
+ +

In CIRRUS_BLTMODE_MEMSYSSRC mode the bitblit copy routine + cirrus_bitblt_cputovideo fails to check wethehr the specified memory + region is safe. +

+
+ +

A local attacker could potentially execute arbitrary code with + privileges of Xen (QEMU) process on the host, gain privileges on the host + system, or cause a Denial of Service condition. +

+
+ +

Running guests in Paravirtualization (PV) mode, or running guests in + Hardware-assisted virtualizion (HVM) utilizing stub domains mitigate + the issue. +

+ +

Running HVM guests with the device model in a stubdomain will mitigate + the issue. +

+ +

Changing the video card emulation to stdvga (stdvga=1, vga=”stdvga”, + in the xl domain configuration) will avoid the vulnerability. +

+
+ +

All Xen Tools users should upgrade to the latest version:

+ + + # emerge --sync + # emerge --ask --oneshot --verbose + ">=app-emulation/xen-tools-4.7.1-r8" + + +
+ + CVE-2017-2620 + + BlueKnight + whissi +
diff --git a/sdk_container/src/third_party/portage-stable/metadata/glsa/timestamp.chk b/sdk_container/src/third_party/portage-stable/metadata/glsa/timestamp.chk index 98f5de2268..b8e8cb3734 100644 --- a/sdk_container/src/third_party/portage-stable/metadata/glsa/timestamp.chk +++ b/sdk_container/src/third_party/portage-stable/metadata/glsa/timestamp.chk @@ -1 +1 @@ -Tue, 21 Mar 2017 21:38:55 +0000 +Fri, 07 Apr 2017 21:09:29 +0000