December 2018 - Arch-security - lists.archlinux.org

[ASA-201812-12] go-pie: multiple issues
by Remi Gacogne 29 Dec '18

29 Dec '18

Arch Linux Security Advisory ASA-201812-12 ========================================== Severity: High Date : 2018-12-18 CVE-ID : CVE-2018-16873 CVE-2018-16874 CVE-2018-16875 Package : go-pie Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-835 Summary ======= The package go-pie before version 2:1.11.3-1 is vulnerable to multiple issues including arbitrary command execution, directory traversal and denial of service. Resolution ========== Upgrade to 2:1.11.3-1. # pacman -Syu "go-pie>=2:1.11.3-1" The problems have been fixed upstream in version 1.11.3. Workaround ========== None. Description =========== - CVE-2018-16873 (arbitrary command execution) 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-16874 (directory traversal) 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-16875 (denial of service) 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. Impact ====== A remote attacker can execute arbitrary code or perform a denial of service attack. References ========== https://groups.google.com/forum/#!msg/golang-announce/Kw31K8G7Fi0/z2olKn-QC… https://github.com/golang/go/issues/29230 https://github.com/golang/go/commit/8954addb3294a5e664a9833354bafa58f163fe8f https://github.com/golang/go/commit/5aedc8af94c0a8ffc58cbd09993192dea9b238db https://github.com/golang/go/issues/29231 https://github.com/golang/go/commit/90d609ba6156299642d08afc06d85ab770a03972 https://github.com/golang/go/issues/29233 https://github.com/golang/go/commit/df523969435b8945d939c7e2a849b50910ef4c25 https://security.archlinux.org/CVE-2018-16873 https://security.archlinux.org/CVE-2018-16874 https://security.archlinux.org/CVE-2018-16875

1 0

[ASA-201812-11] go: multiple issues
by Remi Gacogne 29 Dec '18

29 Dec '18

Arch Linux Security Advisory ASA-201812-11 ========================================== Severity: High Date : 2018-12-18 CVE-ID : CVE-2018-16873 CVE-2018-16874 CVE-2018-16875 Package : go Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-835 Summary ======= The package go before version 2:1.11.3-1 is vulnerable to multiple issues including arbitrary command execution, directory traversal and denial of service. Resolution ========== Upgrade to 2:1.11.3-1. # pacman -Syu "go>=2:1.11.3-1" The problems have been fixed upstream in version 1.11.3. Workaround ========== None. Description =========== - CVE-2018-16873 (arbitrary command execution) 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-16874 (directory traversal) 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-16875 (denial of service) 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. Impact ====== A remote attacker can execute arbitrary code or perform a denial of service attack. References ========== https://groups.google.com/forum/#!msg/golang-announce/Kw31K8G7Fi0/z2olKn-QC… https://github.com/golang/go/issues/29230 https://github.com/golang/go/commit/8954addb3294a5e664a9833354bafa58f163fe8f https://github.com/golang/go/commit/5aedc8af94c0a8ffc58cbd09993192dea9b238db https://github.com/golang/go/issues/29231 https://github.com/golang/go/commit/90d609ba6156299642d08afc06d85ab770a03972 https://github.com/golang/go/issues/29233 https://github.com/golang/go/commit/df523969435b8945d939c7e2a849b50910ef4c25 https://security.archlinux.org/CVE-2018-16873 https://security.archlinux.org/CVE-2018-16874 https://security.archlinux.org/CVE-2018-16875

1 0

[ASA-201812-10] webkit2gtk: arbitrary code execution
by Remi Gacogne 29 Dec '18

29 Dec '18

Arch Linux Security Advisory ASA-201812-10 ========================================== Severity: Critical Date : 2018-12-14 CVE-ID : CVE-2018-4437 Package : webkit2gtk Type : arbitrary code execution Remote : Yes Link : https://security.archlinux.org/AVG-834 Summary ======= The package webkit2gtk before version 2.22.5-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 2.22.5-1. # pacman -Syu "webkit2gtk>=2.22.5-1" The problem has been fixed upstream in version 2.22.5. Workaround ========== None. Description =========== Multiple memory corruption issues have been found in WebKitGTK+ before 2.22.5, where processing maliciously crafted web content may lead to arbitrary code execution. Impact ====== A remote attacker can execute arbitrary code via crafted web content. References ========== https://webkitgtk.org/security/WSA-2018-0009.html https://webkitgtk.org/security/WSA-2018-0009.html#CVE-2018-4437 https://security.archlinux.org/CVE-2018-4437

1 0

[ASA-201812-9] firefox: multiple issues
by Remi Gacogne 12 Dec '18

12 Dec '18

Arch Linux Security Advisory ASA-201812-9 ========================================= Severity: Critical Date : 2018-12-12 CVE-ID : CVE-2018-12405 CVE-2018-12406 CVE-2018-12407 CVE-2018-17466 CVE-2018-18492 CVE-2018-18493 CVE-2018-18494 CVE-2018-18495 CVE-2018-18497 Package : firefox Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-833 Summary ======= The package firefox before version 64.0-1 is vulnerable to multiple issues including arbitrary code execution, same-origin policy bypass and access restriction bypass. Resolution ========== Upgrade to 64.0-1. # pacman -Syu "firefox>=64.0-1" The problems have been fixed upstream in version 64.0. Workaround ========== None. Description =========== - CVE-2018-12405 (arbitrary code execution) Several memory safety bugs have been found in Firefox < 64.0. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could be exploited to run arbitrary code. - CVE-2018-12406 (arbitrary code execution) Several memory safety bugs have been found in Firefox < 64.0. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could be exploited to run arbitrary code. - CVE-2018-12407 (arbitrary code execution) A buffer overflow has been found in the Angle library used for WebGL content by Firefox < 64.0, when drawing and validating elements with the VertexBuffer11 module. - CVE-2018-17466 (arbitrary code execution) A buffer overflow and out-of-bounds read has been found in the TextureStorage11 function of the Angle library, as used in the chromium browser before 70.0.3538.67 and Firefox before 64.0. - CVE-2018-18492 (arbitrary code execution) A use-after-free has been found in Firefox < 64.0, after deleting a selection element due to a weak reference to the select element in the options collection. - CVE-2018-18493 (arbitrary code execution) A buffer overflow can occur in the Skia library use by Firefox < 64.0, during buffer offset calculations with hardware accelerated canvas 2D actions due to the use of 32-bit calculations instead of 64-bit. - CVE-2018-18494 (same-origin policy bypass) A same-origin policy violation has been found in Firefox < 64.0, allowing the theft of cross-origin URL entries when using the Javascript location property to cause a redirection to another site using performance.getEntries(). - CVE-2018-18495 (access restriction bypass) A security issue has been found in Firefox < 64.0, where WebExtension content scripts can be loaded into about: pages in some circumstances, in violation of the permissions granted to extensions. This could allow an extension to interfere with the loading and usage of these pages and use capabilities that were intended to be restricted from extensions. - CVE-2018-18497 (access restriction bypass) A security issue has been found in Firefox < 64.0, where limitations on the URIs allowed to WebExtensions by the browser.windows.create API can be bypassed when a pipe in the URL field is used within the extension to load multiple pages as a single argument. This could allow a malicious WebExtension to opened privileged about: or file: locations. Impact ====== A remote attacker can access sensitive information, bypass security measures and execute arbitrary code on the affected host. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-124… https://bugzilla.mozilla.org/buglist.cgi?bug_id=1494752%2C1498765%2C1503326… https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-124… https://bugzilla.mozilla.org/buglist.cgi?bug_id=1456947%2C1475669%2C1504816… https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-124… https://bugzilla.mozilla.org/show_bug.cgi?id=1505973 https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-des… https://bugs.chromium.org/p/chromium/issues/detail?id=880906 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-174… https://bugzilla.mozilla.org/show_bug.cgi?id=1488295 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-184… https://bugzilla.mozilla.org/show_bug.cgi?id=1499861 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-184… https://bugzilla.mozilla.org/show_bug.cgi?id=1504452 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-184… https://bugzilla.mozilla.org/show_bug.cgi?id=1487964 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-184… https://bugzilla.mozilla.org/show_bug.cgi?id=1427585 https://www.mozilla.org/en-US/security/advisories/mfsa2018-29/#CVE-2018-184… https://bugzilla.mozilla.org/show_bug.cgi?id=1488180 https://security.archlinux.org/CVE-2018-12405 https://security.archlinux.org/CVE-2018-12406 https://security.archlinux.org/CVE-2018-12407 https://security.archlinux.org/CVE-2018-17466 https://security.archlinux.org/CVE-2018-18492 https://security.archlinux.org/CVE-2018-18493 https://security.archlinux.org/CVE-2018-18494 https://security.archlinux.org/CVE-2018-18495 https://security.archlinux.org/CVE-2018-18497

1 0

[ASA-201812-8] openssl-1.0: private key recovery
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-8 ========================================= Severity: Low Date : 2018-12-08 CVE-ID : CVE-2018-0734 CVE-2018-5407 Package : openssl-1.0 Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-807 Summary ======= The package openssl-1.0 before version 1.0.2.q-1 is vulnerable to private key recovery. Resolution ========== Upgrade to 1.0.2.q-1. # pacman -Syu "openssl-1.0>=1.0.2.q-1" The problems have been fixed upstream in version 1.0.2.q. Workaround ========== None. Description =========== - CVE-2018-0734 (private key recovery) A timing vulnerability has been found in DSA signature generation in openssl versions up to and including 1.1.1, where information is leaked via a side channel when a BN is resized and could lead to private key recovery. - CVE-2018-5407 (private key recovery) A vulnerability has been found in the ECC scalar multiplication implementation of OpenSSL < 1.1.0i and <= 1.0.2p. The implementation, used in e.g. ECDSA and ECDH, has been shown to be vulnerable to a microarchitecture timing side channel attack. An attacker with sufficient access to mount local timing attacks during ECDSA signature generation could recover the private key. Impact ====== A remote attacker might be able to recover a private DSA key via a timing attack. In addition, a local attacker might be able to recover a private ECC key via a timing attack. References ========== https://www.openssl.org/news/secadv/20181030.txt https://github.com/openssl/openssl/commit/8abfe72e8c1de1b95f50aa0d9134803b4… https://github.com/openssl/openssl/pull/7486 https://www.openssl.org/news/secadv/20181112.txt https://github.com/openssl/openssl/commit/b18162a7c9bbfb57112459a4d6631fa25… https://security.archlinux.org/CVE-2018-0734 https://security.archlinux.org/CVE-2018-5407

1 0

[ASA-201812-7] lib32-openssl-1.0: private key recovery
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-7 ========================================= Severity: Low Date : 2018-12-08 CVE-ID : CVE-2018-0734 CVE-2018-5407 Package : lib32-openssl-1.0 Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-806 Summary ======= The package lib32-openssl-1.0 before version 1.0.2.q-1 is vulnerable to private key recovery. Resolution ========== Upgrade to 1.0.2.q-1. # pacman -Syu "lib32-openssl-1.0>=1.0.2.q-1" The problems have been fixed upstream in version 1.0.2.q. Workaround ========== None. Description =========== - CVE-2018-0734 (private key recovery) A timing vulnerability has been found in DSA signature generation in openssl versions up to and including 1.1.1, where information is leaked via a side channel when a BN is resized and could lead to private key recovery. - CVE-2018-5407 (private key recovery) A vulnerability has been found in the ECC scalar multiplication implementation of OpenSSL < 1.1.0i and <= 1.0.2p. The implementation, used in e.g. ECDSA and ECDH, has been shown to be vulnerable to a microarchitecture timing side channel attack. An attacker with sufficient access to mount local timing attacks during ECDSA signature generation could recover the private key. Impact ====== A remote attacker might be able to recover a private DSA key via a timing attack. In addition, a local attacker might be able to recover a private ECC key via a timing attack. References ========== https://www.openssl.org/news/secadv/20181030.txt https://github.com/openssl/openssl/commit/8abfe72e8c1de1b95f50aa0d9134803b4… https://github.com/openssl/openssl/pull/7486 https://www.openssl.org/news/secadv/20181112.txt https://github.com/openssl/openssl/commit/b18162a7c9bbfb57112459a4d6631fa25… https://security.archlinux.org/CVE-2018-0734 https://security.archlinux.org/CVE-2018-5407

1 0

[ASA-201812-6] lib32-openssl: private key recovery
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-6 ========================================= Severity: Low Date : 2018-12-08 CVE-ID : CVE-2018-0734 CVE-2018-0735 Package : lib32-openssl Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-793 Summary ======= The package lib32-openssl before version 1:1.1.1.a-1 is vulnerable to private key recovery. Resolution ========== Upgrade to 1:1.1.1.a-1. # pacman -Syu "lib32-openssl>=1:1.1.1.a-1" The problems have been fixed upstream in version 1.1.1.a. Workaround ========== None. Description =========== - CVE-2018-0734 (private key recovery) A timing vulnerability has been found in DSA signature generation in openssl versions up to and including 1.1.1, where information is leaked via a side channel when a BN is resized and could lead to private key recovery. - CVE-2018-0735 (private key recovery) The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack in openssl versions prior to 1.1.1a. An attacker could use variations in the signing algorithm to recover the private key. Impact ====== A remote attacker might be able to recover a private ECDSA or DSA key via a timing attack. References ========== https://www.openssl.org/news/secadv/20181029.txt https://www.openssl.org/news/secadv/20181030.txt https://github.com/openssl/openssl/commit/8abfe72e8c1de1b95f50aa0d9134803b4… https://github.com/openssl/openssl/pull/7486 https://github.com/openssl/openssl/commit/b1d6d55ece1c26fa2829e2b819b038d7b… https://security.archlinux.org/CVE-2018-0734 https://security.archlinux.org/CVE-2018-0735

1 0

[ASA-201812-5] openssl: private key recovery
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-5 ========================================= Severity: Low Date : 2018-12-08 CVE-ID : CVE-2018-0734 CVE-2018-0735 Package : openssl Type : private key recovery Remote : Yes Link : https://security.archlinux.org/AVG-792 Summary ======= The package openssl before version 1.1.1.a-1 is vulnerable to private key recovery. Resolution ========== Upgrade to 1.1.1.a-1. # pacman -Syu "openssl>=1.1.1.a-1" The problems have been fixed upstream in version 1.1.1.a. Workaround ========== None. Description =========== - CVE-2018-0734 (private key recovery) A timing vulnerability has been found in DSA signature generation in openssl versions up to and including 1.1.1, where information is leaked via a side channel when a BN is resized and could lead to private key recovery. - CVE-2018-0735 (private key recovery) The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack in openssl versions prior to 1.1.1a. An attacker could use variations in the signing algorithm to recover the private key. Impact ====== A remote attacker might be able to recover a private ECDSA or DSA key via a timing attack. References ========== https://www.openssl.org/news/secadv/20181029.txt https://www.openssl.org/news/secadv/20181030.txt https://github.com/openssl/openssl/commit/8abfe72e8c1de1b95f50aa0d9134803b4… https://github.com/openssl/openssl/pull/7486 https://github.com/openssl/openssl/commit/b1d6d55ece1c26fa2829e2b819b038d7b… https://security.archlinux.org/CVE-2018-0734 https://security.archlinux.org/CVE-2018-0735

1 0

[ASA-201812-4] texlive-bin: arbitrary code execution
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-4 ========================================= Severity: High Date : 2018-12-08 CVE-ID : CVE-2018-17407 Package : texlive-bin Type : arbitrary code execution Remote : No Link : https://security.archlinux.org/AVG-770 Summary ======= The package texlive-bin before version 2018.48691-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 2018.48691-1. # pacman -Syu "texlive-bin>=2018.48691-1" The problem has been fixed upstream in version 2018.48691. Workaround ========== None. Description =========== An issue was discovered in t1_check_unusual_charstring functions in writet1.c files in TeX Live before 2018-09-21. A buffer overflow in the handling of Type 1 fonts allows arbitrary code execution when a malicious font is loaded by one of the vulnerable tools: pdflatex, pdftex, dvips, or luatex. Impact ====== A local attacker can execute arbitrary code via a crafted font. References ========== https://github.com/TeX-Live/texlive-source/commit/6ed0077520e2b0da1fd060c7f… https://github.com/TeX-Live/texlive-source/commit/f1211fe16c19af8fee54146ae… https://security.archlinux.org/CVE-2018-17407

1 0

[ASA-201812-3] wireshark-cli: multiple issues
by Jelle van der Waa 11 Dec '18

11 Dec '18

Arch Linux Security Advisory ASA-201812-3 ========================================= Severity: Critical Date : 2018-12-08 CVE-ID : CVE-2018-19622 CVE-2018-19623 CVE-2018-19624 CVE-2018-19625 CVE-2018-19626 CVE-2018-19627 CVE-2018-19628 Package : wireshark-cli Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-825 Summary ======= The package wireshark-cli before version 2.6.5-1 is vulnerable to multiple issues including arbitrary code execution, information disclosure and denial of service. Resolution ========== Upgrade to 2.6.5-1. # pacman -Syu "wireshark-cli>=2.6.5-1" The problems have been fixed upstream in version 2.6.5. Workaround ========== None. Description =========== - CVE-2018-19622 (denial of service) A security issue has been found in the MMSE dissector of Wireshark versions prior to 2.6.5, which could be made to consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19623 (arbitrary code execution) A heap-based out-of-bounds write has been found in the LBMPDM dissector of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19624 (denial of service) A NULL-pointer dereference has been found in the PVFS dissector of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19625 (information disclosure) An out-of-bounds read has been found in the dissection engine of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19626 (information disclosure) An out-of-bounds read has been found in the DCOM dissector of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19627 (information disclosure) An out-of-bounds read has been found in the IxVeriWave file parser of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file - CVE-2018-19628 (denial of service) A divide-by-zero error has been found in the ZigBee ZCL dissector of Wireshark versions prior to 2.6.5, which could be triggered by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file Impact ====== A remote attacker can execute arbitrary code, access sensitive information or crash wireshark via a crafted network packet or a capture file. References ========== https://www.wireshark.org/docs/relnotes/wireshark-2.6.5.html https://www.wireshark.org/security/wnpa-sec-2018-54 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15250 https://code.wireshark.org/review/#/c/30613/ https://www.wireshark.org/security/wnpa-sec-2018-53 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15132 https://code.wireshark.org/review/#/c/30346/ https://www.wireshark.org/security/wnpa-sec-2018-56 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15280 https://code.wireshark.org/review/#/c/30811/ https://www.wireshark.org/security/wnpa-sec-2018-51 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14466 https://code.wireshark.org/review/#/c/30152/ https://www.wireshark.org/security/wnpa-sec-2018-52 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15130 https://code.wireshark.org/review/#/c/30158/ https://www.wireshark.org/security/wnpa-sec-2018-55 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15279 https://code.wireshark.org/review/#/c/30813/ https://www.wireshark.org/security/wnpa-sec-2018-57 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15281 https://code.wireshark.org/review/#/c/30810/ https://security.archlinux.org/CVE-2018-19622 https://security.archlinux.org/CVE-2018-19623 https://security.archlinux.org/CVE-2018-19624 https://security.archlinux.org/CVE-2018-19625 https://security.archlinux.org/CVE-2018-19626 https://security.archlinux.org/CVE-2018-19627 https://security.archlinux.org/CVE-2018-19628

1 0