November 2020 - Arch-security - lists.archlinux.org

[ASA-202011-21] swtpm: privilege escalation
by Morten Linderud 30 Nov '20

30 Nov '20

Arch Linux Security Advisory ASA-202011-21 ========================================== Severity: Medium Date : 2020-11-19 CVE-ID : CVE-2020-28407 Package : swtpm Type : privilege escalation Remote : No Link : https://security.archlinux.org/AVG-1282 Summary ======= The package swtpm before version 0.5.1-1 is vulnerable to privilege escalation. Resolution ========== Upgrade to 0.5.1-1. # pacman -Syu "swtpm>=0.5.1-1" The problem has been fixed upstream in version 0.5.1. Workaround ========== None. Description =========== A potential symbolic link following issue has been found in swtpm before 0.5.1. Impact ====== A malicious file might trick the program to overwrite files and escalate priviledges. References ========== https://github.com/stefanberger/swtpm/compare/v0.5.0...v0.5.1 https://github.com/stefanberger/swtpm/commit/e9c9778d5c35ef077aed1ec6601b47… https://github.com/stefanberger/swtpm/commit/4cc42c0ba3632a98ef381bda68d0a4… https://github.com/stefanberger/swtpm/commit/634b6294000fb785b9f12e13b852c1… https://github.com/stefanberger/swtpm/commit/a03cbadd087b2602412823f254ac75… https://github.com/stefanberger/swtpm/commit/526300236dc8a7664acdc265b6fc5d… https://github.com/stefanberger/swtpm/commit/e621b21d4c31029ebe794350fcff2b… https://security.archlinux.org/CVE-2020-28407

1 0

[ASA-202011-20] raptor: arbitrary code execution
by Morten Linderud 30 Nov '20

30 Nov '20

Arch Linux Security Advisory ASA-202011-20 ========================================== Severity: Medium Date : 2020-11-19 CVE-ID : CVE-2017-18926 CVE-2020-25713 Package : raptor Type : arbitrary code execution Remote : No Link : https://security.archlinux.org/AVG-1283 Summary ======= The package raptor before version 2.0.15-14 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 2.0.15-14. # pacman -Syu "raptor>=2.0.15-14" The problems have been fixed upstream but no release is available yet. Workaround ========== None. Description =========== - CVE-2017-18926 (arbitrary code execution) raptor_xml_writer_start_element_common in raptor_xml_writer.c in Raptor RDF Syntax Library 2.0.15 miscalculates the maximum nspace declarations for the XML writer, leading to heap-based buffer overflows (sometimes seen in raptor_qname_format_as_xml). - CVE-2020-25713 (arbitrary code execution) A malformed input file can lead to a segfault due to an out of bounds array access in raptor_xml_writer_start_element_common. Impact ====== A maliciously crafted RDF file can crash the application or execute arbitrary code. References ========== https://bugs.archlinux.org/task/68613 https://www.openwall.com/lists/oss-security/2017/06/07/1 http://bugs.librdf.org/mantis/view.php?id=617 http://bugs.librdf.org/mantis/view.php?id=618 https://github.com/dajobe/raptor/commit/590681e546cd9aa18d57dc2ea1858cb734a… https://bugs.librdf.org/mantis/view.php?id=650 https://bugs.librdf.org/mantis/file_download.php?file_id=348&type=bug https://security.archlinux.org/CVE-2017-18926 https://security.archlinux.org/CVE-2020-25713

1 0

[ASA-202011-19] libass: arbitrary code execution
by Morten Linderud 30 Nov '20

30 Nov '20

Arch Linux Security Advisory ASA-202011-19 ========================================== Severity: Medium Date : 2020-11-19 CVE-ID : CVE-2020-26682 Package : libass Type : arbitrary code execution Remote : No Link : https://security.archlinux.org/AVG-1285 Summary ======= The package libass before version 0.15.0-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 0.15.0-1. # pacman -Syu "libass>=0.15.0-1" The problem has been fixed upstream in version 0.15.0. Workaround ========== None. Description =========== In libass 0.14.0, the ass_outline_construct's call to outline_stroke causes a signed integer overflow. Impact ====== A maliciously crafted file might crash the application or execute arbitrary code. References ========== https://github.com/libass/libass/issues/431 https://github.com/libass/libass/pull/432 https://github.com/libass/libass/commit/676f9dc5b52ef406c5527bdadbcb947f113… https://security.archlinux.org/CVE-2020-26682

1 0

[ASA-202011-18] c-ares: denial of service
by Morten Linderud 30 Nov '20

30 Nov '20

Arch Linux Security Advisory ASA-202011-18 ========================================== Severity: Medium Date : 2020-11-19 CVE-ID : CVE-2020-8277 Package : c-ares Type : denial of service Remote : Yes Link : https://security.archlinux.org/AVG-1280 Summary ======= The package c-ares before version 1.17.1-1 is vulnerable to denial of service. Resolution ========== Upgrade to 1.17.1-1. # pacman -Syu "c-ares>=1.17.1-1" The problem has been fixed upstream in version 1.17.1. Workaround ========== None. Description =========== An application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service by getting the application to resolve a DNS record with a large number of responses. Impact ====== A remote malicious attacker might be able to crash the application with a crafted DNS response. References ========== https://github.com/c-ares/c-ares/issues/371 https://github.com/c-ares/c-ares/commit/0d252eb3b2147179296a3bdb4ef97883c97… https://security.archlinux.org/CVE-2020-8277

1 0

[ASA-202011-17] rclone: private key recovery
by Morten Linderud 30 Nov '20

30 Nov '20

Arch Linux Security Advisory ASA-202011-17 ========================================== Severity: Medium Date : 2020-11-19 CVE-ID : CVE-2020-28924 Package : rclone Type : private key recovery Remote : No Link : https://security.archlinux.org/AVG-1286 Summary ======= The package rclone before version 1.53.3-1 is vulnerable to private key recovery. Resolution ========== Upgrade to 1.53.3-1. # pacman -Syu "rclone>=1.53.3-1" The problem has been fixed upstream in version 1.53.3. Workaround ========== All passwords generated by rclone 1.49.0 up to 1.53.2 should be changed. Rclone provides a password checker to find weak passwords as a separate tool called passwordcheck. Description =========== An issue was discovered in rclone 1.49.0 up to 1.53.2. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time rclone was started. This limits the entropy of the passwords enormously. These passwords are often used in the crypt backend for encryption of data. It would be possible to make a dictionary of all possible passwords with about 38 million entries per password length. This would make decryption of secret material possible with a plausible amount of effort. NOTE: all passwords generated by affected versions should be changed. Impact ====== A malicious user might be able to brute force the weak passwords. References ========== https://github.com/rclone/rclone/issues/4783 https://github.com/rclone/rclone/commit/7985df37681f54d013816a4641da4f9b085… https://github.com/rclone/passwordcheck https://security.archlinux.org/CVE-2020-28924

1 0

[ASA-202011-16] go: multiple issues
by Morten Linderud 27 Nov '20

27 Nov '20

Arch Linux Security Advisory ASA-202011-16 ========================================== Severity: High Date : 2020-11-17 CVE-ID : CVE-2020-28362 CVE-2020-28366 CVE-2020-28367 Package : go Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-1278 Summary ======= The package go before version 2:1.15.5-1 is vulnerable to multiple issues including arbitrary code execution and denial of service. Resolution ========== Upgrade to 2:1.15.5-1. # pacman -Syu "go>=2:1.15.5-1" The problems have been fixed upstream in version 1.15.5. Workaround ========== None. Description =========== - CVE-2020-28362 (denial of service) A flaw was found in go before 1.15.5 where a number of math/big.Int methods (Div, Exp, DivMod, Quo, Rem, QuoRem, Mod, ModInverse, ModSqrt, Jacobi, and GCD) can panic when provided crafted large inputs. For the panic to happen, the divisor or modulo argument must be larger than 3168 bits (on 32-bit architectures) or 6336 bits (on 64-bit architectures). Multiple math/big.Rat methods are similarly affected. crypto/rsa.VerifyPSS, crypto/rsa.VerifyPKCS1v15, and crypto/dsa.Verify may panic when provided crafted public keys and signatures. crypto/ecdsa and crypto/elliptic operations may only be affected if custom CurveParams with unusually large field sizes (several times larger than the largest supported curve, P-521) are in use. Using crypto/x509.Verify on a crafted X.509 certificate chain can lead to a panic, even if the certificates don’t chain to a trusted root. The chain can be delivered via a crypto/tls connection to a client, or to a server that accepts and verifies client certificates. net/http clients can be made to crash by an HTTPS server, while net/http servers that accept client certificates will recover the panic and are unaffected. Moreover, an application might crash invoking crypto/x509.(*CertificateRequest).CheckSignature on an X.509 certificate request or during a golang.org/x/crypto/otr conversation. Parsing a golang.org/x/crypto/openpgp Entity or verifying a signature may crash. Finally, a golang.org/x/crypto/ssh client can panic due to a malformed host key, while a server could panic if either PublicKeyCallback accepts a malformed public key, or if IsUserAuthority accepts a certificate with a malformed public key. - CVE-2020-28366 (arbitrary code execution) A flaw was found in go beforer 1.15.5 where the go command may execute arbitrary code at build time when cgo is in use. This may occur when running go get on a malicious package, or any other command that builds untrusted code. - CVE-2020-28367 (arbitrary code execution) A flaw was found in go before 1.15.5 where the go command may execute arbitrary code at build time when cgo is in use. This may occur when running go get on a malicious package, or any other command that builds untrusted code. Impact ====== A local attacker might be able to crash the program via a crafted input. In addition a remote attacker might be able to execute arbitrary code when go get is run on a malicious package, or untrusted code is built via any other command. References ========== https://github.com/golang/go/commit/84150d0af193a7ccd733b3c7fa5787f43125cd2d https://github.com/golang/go/issues/42554 https://github.com/golang/go/issues/42562 https://github.com/golang/go/commit/32159824698a82a174b60a6845e8494ae3243102 https://github.com/golang/go/issues/42558 https://github.com/golang/go/commit/ec06b6d6be568ce1591d91a0ea4f14c190d06605 https://security.archlinux.org/CVE-2020-28362 https://security.archlinux.org/CVE-2020-28366 https://security.archlinux.org/CVE-2020-28367

1 0

[ASA-202011-15] libxml2: multiple issues
by Morten Linderud 27 Nov '20

27 Nov '20

Arch Linux Security Advisory ASA-202011-15 ========================================== Severity: Medium Date : 2020-11-17 CVE-ID : CVE-2019-20388 CVE-2020-7595 CVE-2020-24977 Package : libxml2 Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-1263 Summary ======= The package libxml2 before version 2.9.10-6 is vulnerable to multiple issues including denial of service and information disclosure. Resolution ========== Upgrade to 2.9.10-6. # pacman -Syu "libxml2>=2.9.10-6" The problems have been fixed upstream but no release is available yet. Workaround ========== None. Description =========== - CVE-2019-20388 (denial of service) A memory leak was found in the xmlSchemaValidateStream function of libxml2. Applications that use this library may be vulnerable to memory not being freed leading to a denial of service. - CVE-2020-7595 (denial of service) xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation. - CVE-2020-24977 (information disclosure) GNOME project libxml2 <= 2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. Impact ====== A remote attacker might be able to crash an application using libxml2 or access sensitive information via a crafted XML payload. References ========== https://bugs.archlinux.org/task/68510 https://gitlab.gnome.org/GNOME/libxml2/commit/7ffcd44d7e6c46704f8af0321d931… https://gitlab.gnome.org/GNOME/libxml2/commit/0e1a49c8907645d2e155f0d89d4d9… https://gitlab.gnome.org/GNOME/libxml2/commit/50f06b3efb638efb0abd95dc62dca… https://security.archlinux.org/CVE-2019-20388 https://security.archlinux.org/CVE-2020-7595 https://security.archlinux.org/CVE-2020-24977

1 0

[ASA-202011-14] postgresql: multiple issues
by Morten Linderud 27 Nov '20

27 Nov '20

Arch Linux Security Advisory ASA-202011-14 ========================================== Severity: High Date : 2020-11-17 CVE-ID : CVE-2020-25694 CVE-2020-25695 CVE-2020-25696 Package : postgresql Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-1276 Summary ======= The package postgresql before version 12.5-1 is vulnerable to multiple issues including sandbox escape, arbitrary code execution and silent downgrade. Resolution ========== Upgrade to 12.5-1. # pacman -Syu "postgresql>=12.5-1" The problems have been fixed upstream in version 12.5. Workaround ========== None. Description =========== - CVE-2020-25694 (silent downgrade) A security issue has been found in PostgreSQL before 12.5. Many PostgreSQL-provided client applications have options that create additional database connections. Some of those applications reuse only the basic connection parameters (e.g. host, user, port), dropping others. If this drops a security-relevant parameter (e.g. channel_binding, sslmode, requirepeer, gssencmode), the attacker has an opportunity to complete a MITM attack or observe cleartext transmission. Affected applications are clusterdb, pg_dump, pg_restore, psql, reindexdb, and vacuumdb. The vulnerability arises only if one invokes an affected client application with a connection string containing a security-relevant parameter. - CVE-2020-25695 (sandbox escape) A security issue has been found in PostgreSQL before 12.5, where an attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. While promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum and not manually running ANALYZE, CLUSTER, REINDEX, CREATE INDEX, VACUUM FULL, REFRESH MATERIALIZED VIEW, or a restore from output of the pg_dump command. Performance may degrade quickly under this workaround. VACUUM without the FULL option is safe, and all commands are fine when a trusted user owns the target object. - CVE-2020-25696 (arbitrary code execution) A security issue has been found in PostgreSQL before 12.5, where psql's \gset allows overwriting specially treated variables. The \gset meta- command, which sets psql variables based on query results, does not distinguish variables that control psql behavior. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code as the operating system account running psql. Using \gset with a prefix not found among specially treated variables, e.g. any lowercase string, precludes the attack in an unpatched psql. Impact ====== An attacker in position of man-in-the-middle might be able to access sensitive information or even alter SQL commands. A remote, authenticated attacker might be able to escape the PG sandbox and execute arbitrary code on the server. References ========== https://www.postgresql.org/about/news/postgresql-131-125-1110-1015-9620-and… https://security.archlinux.org/CVE-2020-25694 https://security.archlinux.org/CVE-2020-25695 https://security.archlinux.org/CVE-2020-25696

1 0

[ASA-202011-13] wireshark-cli: denial of service
by Morten Linderud 27 Nov '20

27 Nov '20

Arch Linux Security Advisory ASA-202011-13 ========================================== Severity: Low Date : 2020-11-17 CVE-ID : CVE-2020-28030 Package : wireshark-cli Type : denial of service Remote : Yes Link : https://security.archlinux.org/AVG-1258 Summary ======= The package wireshark-cli before version 3.4.0-1 is vulnerable to denial of service. Resolution ========== Upgrade to 3.4.0-1. # pacman -Syu "wireshark-cli>=3.4.0-1" The problem has been fixed upstream in version 3.4.0. Workaround ========== None. Description =========== A resource exhaustion issue has been found in the GQUIC decoder of Wireshark before 3.2.8. Impact ====== A remote attacker might be able to crash Wireshark via a crafted network capture file or packet. References ========== https://www.wireshark.org/security/wnpa-sec-2020-15.html https://gitlab.com/wireshark/wireshark/-/issues/16887 https://gitlab.com/wireshark/wireshark/-/commit/b287e7165e8aa89cde6ae37e7c2… https://security.archlinux.org/CVE-2020-28030

1 0

[ASA-202011-12] firefox: multiple issues
by Remi Gacogne 19 Nov '20

19 Nov '20

Arch Linux Security Advisory ASA-202011-12 ========================================== Severity: Critical Date : 2020-11-17 CVE-ID : CVE-2020-15999 CVE-2020-16012 CVE-2020-26951 CVE-2020-26952 CVE-2020-26953 CVE-2020-26956 CVE-2020-26958 CVE-2020-26959 CVE-2020-26960 CVE-2020-26961 CVE-2020-26962 CVE-2020-26963 CVE-2020-26965 CVE-2020-26967 CVE-2020-26968 CVE-2020-26969 Package : firefox Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-1279 Summary ======= The package firefox before version 83.0-1 is vulnerable to multiple issues including arbitrary code execution, access restriction bypass, content spoofing, cross-site scripting, information disclosure, insufficient validation, denial of service and incorrect calculation. Resolution ========== Upgrade to 83.0-1. # pacman -Syu "firefox>=83.0-1" The problems have been fixed upstream in version 83.0. Workaround ========== None. Description =========== - CVE-2020-15999 (arbitrary code execution) A heap buffer overflow has been found in freetype2 before 2.10.4. Malformed TTF files with PNG sbit glyphs can cause a heap buffer overflow in Load_SBit_Png as libpng uses the original 32-bit values, which are saved in png_struct. If the original width and/or height are greater than 65535, the allocated buffer won't be able to fit the bitmap. - CVE-2020-16012 (information disclosure) An information disclosure issue has been found in Firefox before 83.0 and chromium before 87.0.4280.66. When drawing a transparent image on top of an unknown cross-origin image, the Skia library drawImage function took a variable amount of time depending on the content of the underlying image. This resulted in potential cross-origin information exposure of image content through timing side-channel attacks. - CVE-2020-26951 (access restriction bypass) A parsing and event loading mismatch has been found in Firefox's SVG code before 83.0 and could have allowed load events to fire, even after sanitization. An attacker already capable of exploiting an XSS vulnerability in privileged internal pages could have used this attack to bypass the built-in sanitizer. - CVE-2020-26952 (arbitrary code execution) A security issue has been found in Firefox before 83.0 where incorrect bookkeeping of functions inlined during JIT compilation could have led to memory corruption and a potentially exploitable crash when handling out-of-memory errors. - CVE-2020-26953 (content spoofing) A security issue has been found in Firefox before 83.0 where it was possible to cause the browser to enter fullscreen mode without displaying the security UI; thus making it possible to attempt a phishing attack or otherwise confuse the user. - CVE-2020-26956 (cross-site scripting) A security issue has been found in Firefox before 83.0 where, in some cases, removing HTML elements during sanitization would keep existing SVG event handlers and therefore lead to XSS. - CVE-2020-26958 (access restriction bypass) Firefox before 83.0 did not block execution of scripts with incorrect MIME types when the response was intercepted and cached through a ServiceWorker. This could lead to a cross-site script inclusion vulnerability, or a Content Security Policy bypass. - CVE-2020-26959 (arbitrary code execution) A security issue has been found in Firefox before 83.0 where, during browser shutdown, reference decrementing could have occurred on a previously freed object, resulting in a use-after-free, memory corruption, and a potentially exploitable crash. - CVE-2020-26960 (arbitrary code execution) A security issue has been found in Firefox before 83.0 where, if the Compact() method was called on an nsTArray, the array could have been reallocated without updating other pointers, leading to a potential use-after-free and exploitable crash. - CVE-2020-26961 (insufficient validation) A security issue has been found in Firefox before 83.0 where, when DNS over HTTPS is in use, it intentionally filters RFC1918 and related IP ranges from the responses as these do not make sense coming from a DoH resolver. However when an IPv4 address was mapped through IPv6, these addresses were erroneously let through, leading to a potential DNS Rebinding attack. - CVE-2020-26962 (access restriction bypass) A security issue has been found in Firefox before 83.0, where cross- origin iframes that contained a login form could have been recognized by the login autofill service, and populated. This could have been used in clickjacking attacks, as well as be read across partitions in dynamic first party isolation. - CVE-2020-26963 (denial of service) A denial of service issue has been found in Firefox before 83.0, where repeated calls to the history and location interfaces could have been used to hang the browser. This was addressed by introducing rate- limiting to these API calls. - CVE-2020-26965 (information disclosure) An information disclosure issue has been found in Firefox before 83.0. Some websites have a feature "Show Password" where clicking a button will change a password field into a textbox field, revealing the typed password. If, when using a software keyboard that remembers user input, a user typed their password and used that feature, the type of the password field was changed, resulting in a keyboard layout change and the possibility for the software keyboard to remember the typed password. - CVE-2020-26967 (incorrect calculation) A security issue has been found in Firefox before 83.0 where, when listening for page changes with a Mutation Observer, a malicious web page could confuse Firefox Screenshots into interacting with elements other than those that it injected into the page. This would lead to internal errors and unexpected behavior in the Screenshots code. - CVE-2020-26968 (arbitrary code execution) Several memory safety issues have been found in Firefox before 83.0 and Firefox ESR before 78.4. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could have been exploited to run arbitrary code. - CVE-2020-26969 (arbitrary code execution) Several memory safety issues have been found in Firefox before 83.0. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could have been exploited to run arbitrary code. Impact ====== A remote attacker might be able to access sensitive information, bypass security measures, trick a user into performing unwanted actions, crash the browser or execute arbitrary code. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/ http://git.savannah.nongnu.org/cgit/freetype/freetype2.git/commit/?id=a3bab… https://savannah.nongnu.org/bugs/?59308 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-160… https://bugzilla.mozilla.org/show_bug.cgi?id=1642028 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1667113 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1667685 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1656741 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1669355 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1669466 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1670358 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1672528 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=610997 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1314912 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1661617 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/show_bug.cgi?id=1665820 https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/buglist.cgi?bug_id=1551615%2C1607762%2C1656697… https://www.mozilla.org/en-US/security/advisories/mfsa2020-50/#CVE-2020-269… https://bugzilla.mozilla.org/buglist.cgi?bug_id=1623920%2C1651705%2C1667872… https://security.archlinux.org/CVE-2020-15999 https://security.archlinux.org/CVE-2020-16012 https://security.archlinux.org/CVE-2020-26951 https://security.archlinux.org/CVE-2020-26952 https://security.archlinux.org/CVE-2020-26953 https://security.archlinux.org/CVE-2020-26956 https://security.archlinux.org/CVE-2020-26958 https://security.archlinux.org/CVE-2020-26959 https://security.archlinux.org/CVE-2020-26960 https://security.archlinux.org/CVE-2020-26961 https://security.archlinux.org/CVE-2020-26962 https://security.archlinux.org/CVE-2020-26963 https://security.archlinux.org/CVE-2020-26965 https://security.archlinux.org/CVE-2020-26967 https://security.archlinux.org/CVE-2020-26968 https://security.archlinux.org/CVE-2020-26969

1 0