- Arch-security - lists.archlinux.org

[arch-security] [ASA-201603-2] openssl: multiple issues
by Levente Polyak 07 Mar '16

07 Mar '16

Arch Linux Security Advisory ASA-201603-2 ========================================= Severity: High Date : 2016-03-07 CVE-ID : CVE-2016-0702 CVE-2016-0705 CVE-2016-0797 CVE-2016-0798 CVE-2016-0799 CVE-2016-0800 Package : openssl Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package openssl before version 1.0.2.g-3 is vulnerable to multiple issues including but not limited to private key extraction, denial of service, arbitrary code execution, resource consumption and cross-protocol attacks leading to cipher text decryption. Resolution ========== Upgrade to 1.0.2.g-3. # pacman -Syu "openssl>=1.0.2.g-3" The problems have been fixed upstream in version 1.0.2.g-3. Workaround ========== None. Description =========== - CVE-2016-0702 (private key extraction) A side-channel attack was found that makes use of cache-bank conflicts on the Intel Sandy-Bridge microarchitecture. An attacker who has the ability to control code in a thread running on the same hyper-threaded core as the victim's thread that is performing decryption, could use this flaw to recover RSA private keys. - CVE-2016-0705 (denial of service) A double-free flaw was found in the way OpenSSL parsed certain malformed DSA (Digital Signature Algorithm) private keys. An attacker could create specially crafted DSA private keys that, when processed by an application compiled against OpenSSL, could cause the application to crash. - CVE-2016-0797 (arbitrary code execution) An integer overflow flaw, leading to a NULL pointer dereference or a heap-based memory corruption, was found in the way some BIGNUM functions of OpenSSL were implemented. Applications that use these functions with large untrusted input could crash or, potentially, execute arbitrary code. - CVE-2016-0798 (resource consumption) A memory leak flaw was found in the way OpenSSL performed SRP user database look-ups using the SRP_VBASE_get_by_user() function. A remote attacker connecting to certain SRP servers with an invalid user name could leak approximately 300 bytes of the server's memory per connection. - CVE-2016-0799 (denial of service) The fmtstr function in crypto/bio/b_print.c improperly calculates string lengths, which allows remote attackers to cause a denial of service (overflow and out-of-bounds read) or possibly have unspecified other impact via a long string, as demonstrated by a large amount of ASN.1 data, a different vulnerability than CVE-2016-2842. - CVE-2016-0800 (cross-protocol attack) A padding oracle flaw was found in the Secure Sockets Layer version 2.0 (SSLv2) protocol. An attacker can potentially use this flaw to decrypt RSA-encrypted cipher text from a connection using a newer SSL/TLS protocol version, allowing them to decrypt such connections. This cross-protocol attack is publicly referred to as DROWN. Impact ====== A remote attacker is able to use multiple issues to perform a denial of service attack, trigger a memory leak resulting in resource consumption, use a cross-protocol attack that is leading to cipher text decryption or possibly execute arbitrary code under certain circumstances. Furthermore a local attacker may be able to extract the RSA private key by running code in a thread that is running on the same hyper-threaded core as the victim's thread that is performing decryption. References ========== https://www.openssl.org/news/secadv/20160301.txt https://access.redhat.com/security/cve/CVE-2016-0702 https://access.redhat.com/security/cve/CVE-2016-0705 https://access.redhat.com/security/cve/CVE-2016-0797 https://access.redhat.com/security/cve/CVE-2016-0798 https://access.redhat.com/security/cve/CVE-2016-0799 https://access.redhat.com/security/cve/CVE-2016-0800

1 0

[arch-security] [ASA-201603-1] chromium: multiple issues
by Remi Gacogne 03 Mar '16

03 Mar '16

Arch Linux Security Advisory ASA-201603-1 ========================================= Severity: High Date : 2016-03-03 CVE-ID : CVE-2015-8126 CVE-2016-1630 CVE-2016-1631 CVE-2016-1632 CVE-2016-1633 CVE-2016-1634 CVE-2016-1635 CVE-2016-1636 CVE-2016-1637 CVE-2016-1638 CVE-2016-1639 CVE-2016-1640 CVE-2016-1641 CVE-2016-1642 Package : chromium Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package chromium before version 49.0.2623.75-1 is vulnerable to multiple issues. Resolution ========== Upgrade to 49.0.2623.75-1. # pacman -Syu "chromium>=49.0.2623.75-1" The problem has been fixed upstream in version 49.0.2623.75. Workaround ========== None. Description =========== - CVE-2015-8126: Buffer overflow vulnerabilities in functions png_get_PLTE/png_set_PLTE, allowing remote attackers to cause DoS to application or have unspecified other impact. These functions failed to check for an out-of-range palette when reading or writing PNG files with a bit_depth less than 8. Some applications might read the bit depth from the IHDR chunk and allocate memory for a 2^N entry palette, while libpng can return a palette with up to 256 entries even when the bit depth is less than 8. - CVE-2016-1630: Same-origin bypass in Blink. Credit to Mariusz Mlynski. - CVE-2016-1631: Same-origin bypass in Pepper Plugin. Credit to Mariusz Mlynski. - CVE-2016-1632: Bad cast in Extensions. - CVE-2016-1633, CVE-2016-1634: Use-after-free in Blink. Credit to cloudfuzzer. - CVE-2016-1635: Use-after-free in Blink. Credit to Rob Wu. - CVE-2016-1636: SRI Validation Bypass. Credit to Ryan Lester and Bryant Zadegan. - CVE-2016-1637: Information Leak in Skia. Credit to Keve Nagy. - CVE-2016-1638: WebAPI Bypass. Credit to Rob Wu. - CVE-2016-1639: Use-after-free in WebRTC. Credit to Khalil Zhani. - CVE-2016-1640: Origin confusion in Extensions UI. Credit to Luan Herrera. - CVE-2016-1641: Use-after-free in Favicon. Credit to Atte Kettunen of OUSPG. - CVE-2016-1642: Various fixes from internal audits, fuzzing and other initiatives. Impact ====== A remote attacker can bypass restrictions like the same-origin policy and the WebAPI restrictions, or have other unspecified impact. References ========== http://googlechromereleases.blogspot.fr/2016/03/stable-channel-update.html https://access.redhat.com/security/cve/CVE-2015-8126 https://access.redhat.com/security/cve/CVE-2016-1630 https://access.redhat.com/security/cve/CVE-2016-1631 https://access.redhat.com/security/cve/CVE-2016-1632 https://access.redhat.com/security/cve/CVE-2016-1633 https://access.redhat.com/security/cve/CVE-2016-1634 https://access.redhat.com/security/cve/CVE-2016-1635 https://access.redhat.com/security/cve/CVE-2016-1636 https://access.redhat.com/security/cve/CVE-2016-1637 https://access.redhat.com/security/cve/CVE-2016-1638 https://access.redhat.com/security/cve/CVE-2016-1639 https://access.redhat.com/security/cve/CVE-2016-1640 https://access.redhat.com/security/cve/CVE-2016-1641 https://access.redhat.com/security/cve/CVE-2016-1642

1 0

[arch-security] [ASA-201602-24] cacti: sql injection
by Christian Rebischke 28 Feb '16

28 Feb '16

Arch Linux Security Advisory ASA-201602-24 ========================================== Severity: High Date : 2016-02-28 CVE-ID : CVE-2015-8604 CVE-2015-8377 CVE-2015-8369 Package : cacti Type : sql injection Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package cacti before version 0.8.8_g-2 is vulnerable to sql injection. Resolution ========== Upgrade to 0.8.8_g-2. # pacman -Syu "cacti>=0.8.8_g-2" The problem has been fixed upstream in version 0.8.8_g. Workaround ========== None. Description =========== - CVE-2015-8604 (sql injection) SQL injection in graphs_new.php. - CVE-2015-8377 (sql injection) SQL injection vulnerability in the host_new_graphs_save function in graphs_new.php. - CVE-2015-8369 (sql injection) SQL injection in graph.php. Impact ====== A remote attacker is able to get access to the cacti database. References ========== http://www.openwall.com/lists/oss-security/2016/01/04/8 https://bugs.mageia.org/show_bug.cgi?id=17352 http://www.cacti.net/release_notes_0_8_8g.php

1 0

[arch-security] [ASA-201602-23] lib32-glibc: unbound stack usage
by Christian Rebischke 28 Feb '16

28 Feb '16

Arch Linux Security Advisory ASA-201602-22 ========================================== Severity: Medium Date : 2016-02-28 CVE-ID : CVE-2014-9761 Package : lib32-glibc Type : unbound stack usage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package lib32-glibc before version 2.23-1 is vulnerable to unbound stack usage. Resolution ========== Upgrade to 2.23-1. # pacman -Syu "lib32-glibc>=2.23-1" The problem has been fixed upstream in version 2.23. Workaround ========== None. Description =========== - CVE-2014-9761 (unbound stack usage) The nan, nanf and nanl functions no longer have unbounded stack usage depending on the length of the string passed as an argument to the functions. Impact ====== An attacker has an easy job with stack based exploits. References ========== https://access.redhat.com/security/cve/CVE-2014-9761 http://seclists.org/oss-sec/2016/q1/153

1 0

[arch-security] [ASA-201602-22] glibc: unbound stack usage
by Christian Rebischke 28 Feb '16

28 Feb '16

Arch Linux Security Advisory ASA-201602-22 ========================================== Severity: Medium Date : 2016-02-28 CVE-ID : CVE-2014-9761 Package : glibc Type : unbound stack usage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package glibc before version 2.23-1 is vulnerable to unbound stack usage. Resolution ========== Upgrade to 2.23-1. # pacman -Syu "glibc>=2.23-1" The problem has been fixed upstream in version 2.23. Workaround ========== None. Description =========== - CVE-2014-9761 (unbound stack usage) The nan, nanf and nanl functions no longer have unbounded stack usage depending on the length of the string passed as an argument to the functions. Impact ====== An attacker has an easy job with stack based exploits. References ========== https://access.redhat.com/security/cve/CVE-2014-9761 http://seclists.org/oss-sec/2016/q1/153

1 0

[arch-security] [ASA-201602-21] lib32-libssh2: man-in-the-middle
by Levente Polyak 25 Feb '16

25 Feb '16

Arch Linux Security Advisory ASA-201602-21 ========================================== Severity: High Date : 2016-02-25 CVE-ID : CVE-2016-0787 Package : lib32-libssh2 Type : man-in-the-middle Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package lib32-libssh2 before version 1.7.0-1 is vulnerable to man-in-the-middle. Resolution ========== Upgrade to 1.7.0-1. # pacman -Syu "lib32-libssh2>=1.7.0-1" The problem has been fixed upstream in version 1.7.0. Workaround ========== This issue may be worked around by using other key exchange methods, such as curve25519-sha256(a)libssh.org or ecdh-sha2-nistp256, both are not vulnerable. By default, an unpatched libssh2 implementation will already attempt to use these two more secure methods when supported by the other party. Description =========== There is a bits/bytes confusion bug resulting in generation of a significantly short ephemeral secret for the diffie-hellman-group1 and diffie-hellman-group14 key exchange methods. The resulting secret is 128 bits long, instead of the recommended sizes of 1024 and 2048 bits respectively. There are practical algorithms (Baby steps/Giant steps, Pollard's rho) that can solve this problem in O(2^63) operations. Using such drastically reduced amount of random bits for Diffie Hellman weakened the handshake security significantly. This vulnerability could be exploited by an eavesdropper with enough resources to decrypt or intercept SSH sessions. Impact ====== A remote attacker is able to use this flaw to decrypt or intercept SSH sessions. References ========== https://www.libssh2.org/adv_20160223.html https://access.redhat.com/security/cve/CVE-2016-0787

1 0

[arch-security] [ASA-201602-20] libssh2: man-in-the-middle
by Levente Polyak 25 Feb '16

25 Feb '16

Arch Linux Security Advisory ASA-201602-20 ========================================== Severity: High Date : 2016-02-25 CVE-ID : CVE-2016-0787 Package : libssh2 Type : man-in-the-middle Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package libssh2 before version 1.7.0-1 is vulnerable to man-in-the-middle. Resolution ========== Upgrade to 1.7.0-1. # pacman -Syu "libssh2>=1.7.0-1" The problem has been fixed upstream in version 1.7.0. Workaround ========== This issue may be worked around by using other key exchange methods, such as curve25519-sha256(a)libssh.org or ecdh-sha2-nistp256, both are not vulnerable. By default, an unpatched libssh2 implementation will already attempt to use these two more secure methods when supported by the other party. Description =========== There is a bits/bytes confusion bug resulting in generation of a significantly short ephemeral secret for the diffie-hellman-group1 and diffie-hellman-group14 key exchange methods. The resulting secret is 128 bits long, instead of the recommended sizes of 1024 and 2048 bits respectively. There are practical algorithms (Baby steps/Giant steps, Pollard's rho) that can solve this problem in O(2^63) operations. Using such drastically reduced amount of random bits for Diffie Hellman weakened the handshake security significantly. This vulnerability could be exploited by an eavesdropper with enough resources to decrypt or intercept SSH sessions. Impact ====== A remote attacker is able to use this flaw to decrypt or intercept SSH sessions. References ========== https://www.libssh2.org/adv_20160223.html https://access.redhat.com/security/cve/CVE-2016-0787

1 0

[arch-security] [ASA-201602-19] libgcrypt: secret key extraction
by Levente Polyak 24 Feb '16

24 Feb '16

Arch Linux Security Advisory ASA-201602-19 ========================================== Severity: High Date : 2016-02-24 CVE-ID : CVE-2015-7511 Package : libgcrypt Type : secret key extraction Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package libgcrypt before version 1.6.5-1 is vulnerable to a side-channel attack leading to extraction of secret decryption keys. Resolution ========== Upgrade to 1.6.5-1. # pacman -Syu "libgcrypt>=1.6.5-1" The problem has been fixed upstream in version 1.6.5. Workaround ========== None. Description =========== A vulnerability was found in a way the ECDH encryption algorithm decrypts data. An attacker with a specialized setup can extract the secret decryption key from a target located in an adjacent room within seconds. This is done by measuring the target's electromagnetic emanations. Impact ====== A remote attacker located in an adjacent room is able to extract the secret decryption key by measuring the target's electromagnetic emanations. References ========== https://access.redhat.com/security/cve/CVE-2015-7511 https://lists.gnupg.org/pipermail/gnupg-announce/2016q1/000384.html https://www.cs.tau.ac.il/~tromer/ecdh/

1 0

[arch-security] [ASA-201602-18] libssh: man-in-the-middle
by Remi Gacogne 23 Feb '16

23 Feb '16

Arch Linux Security Advisory ASA-201602-18 ========================================== Severity: High Date : 2016-02-23 CVE-ID : CVE-2016-0739 Package : libssh Type : man-in-the-middle Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package libssh before version 0.7.3-1 is vulnerable to man-in-the-middle. Resolution ========== Upgrade to 0.7.3-1. # pacman -Syu "libssh>=0.7.3-1" The problem has been fixed upstream in version 0.7.3. Workaround ========== This issue may be worked around by using other key exchange methods, such as curve25519-sha256(a)libssh.org or ecdh-sha2-nistp256, both are not vulnerable. By default, an unpatched libssh implementation will already attempt to use these two more secure methods when supported by the other party. Description =========== libssh versions 0.1 and above have a bits/bytes confusion bug and generate the an anormaly short ephemeral secret for the diffie-hellman-group1 and diffie-hellman-group14 key exchange methods. The resulting secret is 128 bits long, instead of the recommended sizes of 1024 and 2048 bits respectively. There are practical algorithms (Baby steps/Giant steps, Pollard’s rho) that can solve this problem in O(2^63) operations. Both client and server are are vulnerable, pre-authentication. This vulnerability could be exploited by an eavesdropper with enough resources to decrypt or intercept SSH sessions. The bug was found during an internal code review by Aris Adamantiadis of the libssh team. Impact ====== A remote attacker can use this flaw to decrypt or intercept SSH sessions. References ========== https://www.libssh.org/2016/02/23/libssh-0-7-3-security-and-bugfix-release/ https://access.redhat.com/security/cve/CVE-2016-0739

1 0

[arch-security] [ASA-201602-17] chromium: multiple issues
by Remi Gacogne 21 Feb '16

21 Feb '16

Arch Linux Security Advisory ASA-201602-17 ========================================== Severity: Critical Date : 2016-02-21 CVE-ID : CVE-2016-1629 Package : chromium Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package chromium before version 48.0.2564.116-1 is vulnerable to multiple issues. Resolution ========== Upgrade to 48.0.2564.116-1. # pacman -Syu "chromium>=48.0.2564.116-1" The problem has been fixed upstream in version 48.0.2564.116. Workaround ========== None. Description =========== Same-origin bypass in Blink and Sandbox escape in Chrome. Impact ====== A remote attacker might be able to execute arbitrary code by getting the affected user to visit a specially crafted web page. References ========== http://googlechromereleases.blogspot.fr/2016/02/stable-channel-update_18.ht… https://access.redhat.com/security/cve/CVE-2016-1629

1 0