February 2016 - Arch-security - lists.archlinux.org

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

27 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 27 Feb '16

27 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 27 Feb '16

27 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 24 Feb '16

24 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

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

21 Feb '16

Arch Linux Security Advisory ASA-201602-16 ========================================== Severity: Critical Date : 2016-02-21 CVE-ID : CVE-2015-7575 CVE-2016-1523 CVE-2016-1930 CVE-2016-1931 CVE-2016-1935 Package : thunderbird Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package thunderbird before version 38.6.0-1 is vulnerable to multiple issues. Resolution ========== Upgrade to 38.6.0-1. # pacman -Syu "thunderbird>=38.6.0-1" The problem has been fixed upstream in version 38.6.0. Workaround ========== None. Description =========== - CVE-2015-7575 (man-in-the-middle): Security researcher Karthikeyan Bhargavan reported an issue in Network Security Services (NSS) where MD5 signatures in the server signature within the TLS 1.2 ServerKeyExchange message are still accepted. This is an issue since NSS has officially disallowed the accepting MD5 as a hash algorithm in signatures since 2011. This issues exposes NSS based clients such as Firefox to theoretical collision-based forgery attacks. This issue was fixed in NSS version 3.20.2. - CVE-2016-1523 (remote code execution): Security researcher Holger Fuhrmannek reported that a malicious Graphite "smart font" could circumvent the validation of internal instruction parameters in the Graphite 2 library using special CNTXT_ITEM instructions. This could result in arbitrary code execution. In general this flaw cannot be exploited through email in the Thunderbird product, but is potentially a risk in browser or browser-like contexts. - CVE-2016-1930 (remote code execution): Bob Clary, Christian Holler, Nils Ohlmeier, Gary Kwong, Jesse Ruderman, Carsten Book, and Randell Jesup reported memory safety problems and crashes. In general these flaws cannot be exploited through email in the Thunderbird product because scripting is disabled, but are potentially a risk in browser or browser-like contexts. - CVE-2016-1931 (remote code execution): Bob Clary, Carsten Book, Christian Holler, Nicolas Pierron, Eric Rescorla, Tyson Smith, Gabor Krizsanits, and Randell Jesup reported memory safety problems and crashes. In general these flaws cannot be exploited through email in the Thunderbird product because scripting is disabled, but are potentially a risk in browser or browser-like contexts. - CVE-2016-1935 (remote code execution): Security researcher Aki Helin used the Address Sanitizer tool to find a buffer overflow write when rendering some WebGL content. This leads to a potentially exploitable crash. In general this flaw cannot be exploited through email in the Thunderbird product, but is potentially a risk in browser or browser-like contexts. Impact ====== A remote attacker might be able to access sensitive information by performing a man-in-the-middle attack, or execute arbitrary code on the affected host. References ========== https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#t… https://www.mozilla.org/en-US/security/advisories/mfsa2015-150/ https://www.mozilla.org/en-US/security/advisories/mfsa2016-03/ https://www.mozilla.org/en-US/security/advisories/mfsa2016-14/ https://access.redhat.com/security/cve/CVE-2015-7575 https://access.redhat.com/security/cve/CVE-2016-1523 https://access.redhat.com/security/cve/CVE-2016-1930 https://access.redhat.com/security/cve/CVE-2016-1931 https://access.redhat.com/security/cve/CVE-2016-1935

1 0

[arch-security] [Announcement] Discussion about restricting arch-security for public participation
by Levente Polyak 18 Feb '16

18 Feb '16

Dear arch-security subscribers, Dear arch-general subscribers, the policy of the arch-security mailinglist is currently changed to a restricted advisory announcements only list due to certain reason roughly explained on the arch-devops [0] and arch-dev-public [1] lists. As there was no announcement and discussion about this change yet, we want to invite you to discuss the restriction of the arch-security mailinglist on the CC-ed arch-general list. After making sure you are subscribed to arch-general [2], you can simply reply to this announcement by posting directly to the arch-general mailinglist. Our main goal behind this change is to separate relevant official announcements and advisories from possibly long and frequent discussions. The security teams idea is that each announcement to the arch-security list should be considered as an urgent alert and reviewed as soon as possible, without the need to filter them from general conversations and exchange of "unverified" information. sincerely, Levente (anthraxx) [0] https://lists.archlinux.org/pipermail/arch-devops/2016-January/000007.html [1] https://lists.archlinux.org/pipermail/arch-dev-public/2015-December/027581.… [2] https://lists.archlinux.org/listinfo/arch-general

1 1