From security em unicamp.br Thu Sep 8 09:17:31 2016 From: security em unicamp.br (CSIRT Unicamp) Date: Thu, 8 Sep 2016 09:17:31 -0300 Subject: [SECURITY-L] WordPress 4.6.1 Security and Maintenance Release Message-ID: WordPress 4.6.1 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.6 and earlier are affected by two security issues: a cross-site scripting vulnerability via image filename, reported by SumOfPwn researcher Cengiz Han Sahin; and a path traversal vulnerability in the upgrade package uploader, reported by Dominik Schilling from the WordPress security team. Thank you to the reporters for practicing responsible disclosure. In addition to the security issues above, WordPress 4.6.1 fixes 15 bugs from 4.6. For more information, see the release notes or consult the list of changes. Download WordPress 4.6.1 or venture over to Dashboard ? Updates and simply click ?Update Now.? Sites that support automatic background updates are already beginning to update to WordPress 4.6.1. Font: https://wordpress.org/news/2016/09/wordpress-4-6-1-security-and-maintenance-release/ From security em unicamp.br Wed Sep 21 15:08:15 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Wed, 21 Sep 2016 15:08:15 -0300 Subject: [SECURITY-L] [security-news@drupal.org: [Security-news] Drupal Core - Critical - Multiple Vulnerabilities - SA-CORE-2016-004] Message-ID: <20160921180815.GI10718@unicamp.br> ----- Forwarded message from security-news em drupal.org ----- Date: Wed, 21 Sep 2016 17:36:01 +0000 (UTC) From: security-news em drupal.org To: security-news em drupal.org Subject: [Security-news] Drupal Core - Critical - Multiple Vulnerabilities - SA-CORE-2016-004 View online: https://www.drupal.org/SA-CORE-2016-004 -------- DESCRIPTION --------------------------------------------------------- Users who have rights to edit a node, can set the visibility on comments for that node. * Advisory ID: DRUPAL-SA-CORE-2016-004 * Project: Drupal core [1] * Version:li 8.x * Date: 2016-September-21 * Security risk: 18/25 ( Critical) AC:Basic/A:User/CI:Some/II:Some/E:Proof/TD:Default [2] * Vulnerability: -------- DESCRIPTION --------------------------------------------------------- *Users without "Administer comments" can set comment visibility on nodes they can edit. (Less critical)* Users who have rights to edit a node, can set the visibility on comments for that node. This should be restricted to those who have the administer comments permission. *Cross-site Scripting in http exceptions (critical) * An attacker could create a specially crafted url, which could execute arbitrary code in the victim?s browser if loaded. Drupal was not properly sanitizing an exception *Full config export can be downloaded without administrative permissions (critical) * The system.temporary route would allow the download of a full config export. The full config export should be limited to those with Export configuration permission. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- 8.x -------- SOLUTION ------------------------------------------------------------ Upgrade to Drupal 8.1.10 -------- REPORTED BY --------------------------------------------------------- *Users without "Administer comments" can set comment visibility on nodes they can edit.* * Quintus Maximus [4] * Kier Heyl [5] *XSS in http exceptions* * Ivan [6] *Full config export can be downloaded without administrative permissions * * Anton Shubkin [7] -------- FIXED BY ------------------------------------------------------------ *Users without "Administer comments" can set comment visibility on nodes they can edit.* * Lee Rowlands of the Drupal Security Team [8] * Stefan Ruijsenaars of the Drupal Security Team [9] * Andrey Postnikov [10] * Daniel Wehner [11] *XSS in http exceptions* * xjm of the Drupal Security Team [12] * Daniel Wehner [13] * Alex Pott of the Drupal Security Team [14] * Cash Williams of the Drupal Security Team [15] * Pere Orga of the Drupal Security Team [16] * David Snopek of the Drupal Security Team [17] * Heine Deelstra of the Drupal Security Team *Full config export can be downloaded without administrative permissions * * Nathaniel Catchpole of the Drupal Security Team [18] * Alex Pott of the Drupal Security Team [19] * Anton Shubkin [20] * xjm of the Drupal Security Team [21] * Peter Wolanin of the Drupal Security Team [22] -------- COORDINATED BY ------------------------------------------------------ The Drupal Security Team [23] -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [24]. Learn more about the Drupal Security team and their policies [25], writing secure code for Drupal [26], and securing your site [27]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [28] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] http://www.drupal.org/u/q2u [5] https://www.drupal.org/u/kierheyl [6] https://www.drupal.org/user/556138 [7] https://www.drupal.org/user/1060446 [8] http://www.drupal.org/u/larowlan [9] https://www.drupal.org/u/stefanr-0 [10] https://www.drupal.org/user/118908 [11] https://www.drupal.org/user/99340 [12] https://www.drupal.org/user/65776 [13] https://www.drupal.org/user/99340 [14] https://www.drupal.org/user/157725 [15] https://www.drupal.org/user/421070 [16] https://www.drupal.org/u/pere-orga [17] https://www.drupal.org/u/dsnopek [18] https://www.drupal.org/u/catch [19] https://www.drupal.org/user/157725 [20] https://www.drupal.org/user/1060446 [21] https://www.drupal.org/user/65776 [22] https://www.drupal.org/user/49851 [23] https://www.drupal.org/security-team [24] https://www.drupal.org/contact [25] https://www.drupal.org/security-team [26] https://www.drupal.org/writing-secure-code [27] https://www.drupal.org/security/secure-configuration [28] https://twitter.com/drupalsecurity _______________________________________________ Security-news mailing list Security-news em drupal.org Unsubscribe at https://lists.drupal.org/mailman/listinfo/security-news ----- End forwarded message ----- From security em unicamp.br Thu Sep 22 15:03:34 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Thu, 22 Sep 2016 15:03:34 -0300 Subject: [SECURITY-L] [jmm@debian.org: [SECURITY] [DSA 3673-1] openssl security update] Message-ID: <20160922180334.GH10718@unicamp.br> ----- Forwarded message from Moritz Muehlenhoff ----- Date: Thu, 22 Sep 2016 18:50:14 +0200 From: Moritz Muehlenhoff To: debian-security-announce em lists.debian.org Subject: [SECURITY] [DSA 3673-1] openssl security update ------------------------------------------------------------------------- Debian Security Advisory DSA-3673-1 security em debian.org https://www.debian.org/security/ Moritz Muehlenhoff September 22, 2016 https://www.debian.org/security/faq ------------------------------------------------------------------------- Package : openssl CVE ID : CVE-2016-2177 CVE-2016-2178 CVE-2016-2179 CVE-2016-2180 CVE-2016-2181 CVE-2016-2182 CVE-2016-2183 CVE-2016-6302 CVE-2016-6303 CVE-2016-6304 CVE-2016-6306 Several vulnerabilities were discovered in OpenSSL: CVE-2016-2177 Guido Vranken discovered that OpenSSL uses undefined pointer arithmetic. Additional information can be found at https://www.openssl.org/blog/blog/2016/06/27/undefined-pointer-arithmetic/ CVE-2016-2178 Cesar Pereida, Billy Brumley and Yuval Yarom discovered a timing leak in the DSA code. CVE-2016-2179 / CVE-2016-2181 Quan Luo and the OCAP audit team discovered denial of service vulnerabilities in DTLS. CVE-2016-2180 / CVE-2016-2182 / CVE-2016-6303 Shi Lei discovered an out-of-bounds memory read in TS_OBJ_print_bio() and an out-of-bounds write in BN_bn2dec() and MDC2_Update(). CVE-2016-2183 DES-based cipher suites are demoted from the HIGH group to MEDIUM as a mitigation for the SWEET32 attack. CVE-2016-6302 Shi Lei discovered that the use of SHA512 in TLS session tickets is susceptible to denial of service. CVE-2016-6304 Shi Lei discovered that excessively large OCSP status request may result in denial of service via memory exhaustion. CVE-2016-6306 Shi Lei discovered that missing message length validation when parsing certificates may potentially result in denial of service. For the stable distribution (jessie), these problems have been fixed in version 1.0.1t-1+deb8u4. For the unstable distribution (sid), these problems will be fixed soon. We recommend that you upgrade your openssl packages. Further information about Debian Security Advisories, how to apply these updates to your system and frequently asked questions can be found at: https://www.debian.org/security/ Mailing list: debian-security-announce em lists.debian.org ----- End forwarded message ----- From security em unicamp.br Fri Sep 23 09:40:57 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Fri, 23 Sep 2016 09:40:57 -0300 Subject: [SECURITY-L] [security-advisories@freebsd.org: FreeBSD Security Advisory FreeBSD-SA-16:26.openssl] Message-ID: <20160923124057.GN10718@unicamp.br> ----- Forwarded message from FreeBSD Security Advisories ----- Date: Fri, 23 Sep 2016 08:06:07 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Subject: FreeBSD Security Advisory FreeBSD-SA-16:26.openssl ============================================================================= FreeBSD-SA-16:26.openssl Security Advisory The FreeBSD Project Topic: Multiple OpenSSL vulnerabilities Category: contrib Module: openssl Announced: 2016-09-23 Credits: OpenSSL Project Affects: All supported versions of FreeBSD. Corrected: 2016-09-22 14:57:48 UTC (stable/11, 11.0-STABLE) 2016-09-22 15:55:27 UTC (releng/11.0, 11.0-RELEASE) 2016-09-22 15:05:38 UTC (stable/10, 10.3-STABLE) 2016-09-23 07:48:34 UTC (releng/10.3, 10.3-RELEASE-p8) 2016-09-23 07:48:34 UTC (releng/10.2, 10.2-RELEASE-p21) 2016-09-23 07:48:34 UTC (releng/10.1, 10.1-RELEASE-p38) 2016-09-23 07:44:10 UTC (stable/9, 9.3-STABLE) 2016-09-23 07:48:34 UTC (releng/9.3, 9.3-RELEASE-p46) CVE Name: CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2180, CVE-2016-2181, CVE-2016-2182, CVE-2016-6302, CVE-2016-6303, CVE-2016-6304, CVE-2016-6306 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background FreeBSD includes software from the OpenSSL Project. The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library. II. Problem Description A malicious client can send an excessively large OCSP Status Request extension. If that client continually requests renegotiation, sending a large OCSP Status Request extension each time, then there will be unbounded memory growth on the server. [CVE-2016-6304] An overflow can occur in MDC2_Update() either if called directly or through the EVP_DigestUpdate() function using MDC2. If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. [CVE-2016-6303] If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a DoS attack where a malformed ticket will result in an OOB read which will ultimately crash. [CVE-2016-6302] The function BN_bn2dec() does not check the return value of BN_div_word(). This can cause an OOB write if an application uses this function with an overly large BIGNUM. This could be a problem if an overly large certificate or CRL is printed out from an untrusted source. TLS is not affected because record limits will reject an oversized certificate before it is parsed. [CVE-2016-2182] The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is the total length the OID text representation would use and not the amount of data written. This will result in OOB reads when large OIDs are presented. [CVE-2016-2180] Some calculations of limits in OpenSSL have used undefined pointer arithmetic. This could cause problems with some malloc implementations. [CVE-2016-2177] Operations in the DSA signing algorithm should run in constant time in order to avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that a non-constant time codepath is followed for certain operations. [CVE-2016-2178] In a DTLS connection where handshake messages are delivered out-of-order those messages that OpenSSL is not yet ready to process will be buffered for later use. Under certain circumstances, a flaw in the logic means that those messages do not get removed from the buffer even though the handshake has been completed. An attacker could force up to approx. 15 messages to remain in the buffer when they are no longer required. These messages will be cleared when the DTLS connection is closed. The default maximum size for a message is 100k. Therefore the attacker could force an additional 1500k to be consumed per connection. [CVE-2016-2179] A flaw in the DTLS replay attack protection mechanism means that records that arrive for future epochs update the replay protection "window" before the MAC for the record has been validated. This could be exploited by an attacker by sending a record for the next epoch (which does not have to decrypt or have a valid MAC), with a very large sequence number. This means that all subsequent legitimate packets are dropped causing a denial of service for a specific DTLS connection. [CVE-2016-2181] In OpenSSL 1.0.2 and earlier some missing message length checks can result in OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical DoS risk but this has not been observed in practice on common platforms. [CVE-2016-6306] III. Impact A remote attacker can cause OpenSSL server, regardless whether OCSP is supported, to have unbounded memory growth, and eventually lead to a Denial of Service. [CVE-2016-6304] If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. [CVE-2016-6303] An attacker who can send a malformed ticket to the server can cause an OOB read which will ultimately lead to a crash, resulting in a Denial of Service. [CVE-2016-6302] A local attacker can cause an application that parses overly large certificate or CRL to crash. TLS is not affected. [CVE-2016-2182] A local attacker who can create a specially-crafted time stamp file and pass it through the "ts" command of openssl(1) can cause it to crash. This functionality is not used by the SSL/TLS implementation. [CVE-2016-2180] Some OpenSSL code is questionable to integer overflow, which may lead to heap corruption. [CVE-2016-2177] An attacker may recover the private DSA key by conducting timing attack. [CVE-2016-2178] A remote attacker may cause a DTLS server to exhaust memory, resulting in a Denial of Service. [CVE-2016-2179] A remote attacker who can send DTLS records can cause the server to drop all subsequent packets for a specific connection. [CVE-2016-2181] A remote attacker can, in theory, cause OOB reads if the server enabled client authentication. [CVE-2016-6306] IV. Workaround No workaround is available. V. Solution Perform one of the following: 1) Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date. Restart all daemons that use the library, or reboot the system. 2) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install Restart all daemons that use the library, or reboot the system. 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. [FreeBSD 10.3] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.3.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.3.patch.asc # gpg --verify openssl-10.3.patch.asc [FreeBSD 10.1 and 10.2] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.2.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.2.patch.as # gpg --verify openssl-10.2.patch.asc [FreeBSD 9.3] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-9.3.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-9.3.patch.as # gpg --verify openssl-9.3.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile the operating system using buildworld and installworld as described in . Restart all daemons that use the library, or reboot the system. VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision ------------------------------------------------------------------------- stable/9/ r306229 releng/9.3/ r206230 stable/10/ r306196 releng/10.1/ r206230 releng/10.2/ r206230 releng/10.3/ r206230 stable/11/ r306195 releng/11.0/ r306198 ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at _______________________________________________ freebsd-security-notifications em freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications To unsubscribe, send any mail to "freebsd-security-notifications-unsubscribe em freebsd.org" ----- End forwarded message ----- From security em unicamp.br Wed Sep 28 07:41:02 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Wed, 28 Sep 2016 07:41:02 -0300 Subject: [SECURITY-L] [USN-3088-1] Bind vulnerability Message-ID: <20160928104102.GI18685@unicamp.br> ----- Forwarded message from Marc Deslauriers ----- Date: Tue, 27 Sep 2016 14:08:21 -0400 From: Marc Deslauriers To: ubuntu-security-announce em lists.ubuntu.com Subject: [USN-3088-1] Bind vulnerability ========================================================================== Ubuntu Security Notice USN-3088-1 September 27, 2016 bind9 vulnerability ========================================================================== A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 16.04 LTS - Ubuntu 14.04 LTS - Ubuntu 12.04 LTS Summary: Bind could be made to crash if it received specially crafted network traffic. Software Description: - bind9: Internet Domain Name Server Details: It was discovered that Bind incorrectly handled building responses to certain specially crafted requests. A remote attacker could possibly use this issue to cause Bind to crash, resulting in a denial of service. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 16.04 LTS: bind9 1:9.10.3.dfsg.P4-8ubuntu1.1 Ubuntu 14.04 LTS: bind9 1:9.9.5.dfsg-3ubuntu0.9 Ubuntu 12.04 LTS: bind9 1:9.8.1.dfsg.P1-4ubuntu0.17 In general, a standard system update will make all the necessary changes. References: http://www.ubuntu.com/usn/usn-3088-1 CVE-2016-2776 Package Information: https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-8ubuntu1.1 https://launchpad.net/ubuntu/+source/bind9/1:9.9.5.dfsg-3ubuntu0.9 https://launchpad.net/ubuntu/+source/bind9/1:9.8.1.dfsg.P1-4ubuntu0.17 -- ubuntu-security-announce mailing list ubuntu-security-announce em lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce ----- End forwarded message ----- From security em unicamp.br Fri Sep 23 09:40:59 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Fri, 23 Sep 2016 12:40:59 -0000 Subject: [SECURITY-L] [security-advisories@freebsd.org: FreeBSD Security Advisory FreeBSD-SA-16:26.openssl] Message-ID: <20160923124057.GN10718@unicamp.br> ----- Forwarded message from FreeBSD Security Advisories ----- Date: Fri, 23 Sep 2016 08:06:07 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Subject: FreeBSD Security Advisory FreeBSD-SA-16:26.openssl ============================================================================= FreeBSD-SA-16:26.openssl Security Advisory The FreeBSD Project Topic: Multiple OpenSSL vulnerabilities Category: contrib Module: openssl Announced: 2016-09-23 Credits: OpenSSL Project Affects: All supported versions of FreeBSD. Corrected: 2016-09-22 14:57:48 UTC (stable/11, 11.0-STABLE) 2016-09-22 15:55:27 UTC (releng/11.0, 11.0-RELEASE) 2016-09-22 15:05:38 UTC (stable/10, 10.3-STABLE) 2016-09-23 07:48:34 UTC (releng/10.3, 10.3-RELEASE-p8) 2016-09-23 07:48:34 UTC (releng/10.2, 10.2-RELEASE-p21) 2016-09-23 07:48:34 UTC (releng/10.1, 10.1-RELEASE-p38) 2016-09-23 07:44:10 UTC (stable/9, 9.3-STABLE) 2016-09-23 07:48:34 UTC (releng/9.3, 9.3-RELEASE-p46) CVE Name: CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2180, CVE-2016-2181, CVE-2016-2182, CVE-2016-6302, CVE-2016-6303, CVE-2016-6304, CVE-2016-6306 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background FreeBSD includes software from the OpenSSL Project. The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library. II. Problem Description A malicious client can send an excessively large OCSP Status Request extension. If that client continually requests renegotiation, sending a large OCSP Status Request extension each time, then there will be unbounded memory growth on the server. [CVE-2016-6304] An overflow can occur in MDC2_Update() either if called directly or through the EVP_DigestUpdate() function using MDC2. If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. [CVE-2016-6303] If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a DoS attack where a malformed ticket will result in an OOB read which will ultimately crash. [CVE-2016-6302] The function BN_bn2dec() does not check the return value of BN_div_word(). This can cause an OOB write if an application uses this function with an overly large BIGNUM. This could be a problem if an overly large certificate or CRL is printed out from an untrusted source. TLS is not affected because record limits will reject an oversized certificate before it is parsed. [CVE-2016-2182] The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is the total length the OID text representation would use and not the amount of data written. This will result in OOB reads when large OIDs are presented. [CVE-2016-2180] Some calculations of limits in OpenSSL have used undefined pointer arithmetic. This could cause problems with some malloc implementations. [CVE-2016-2177] Operations in the DSA signing algorithm should run in constant time in order to avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that a non-constant time codepath is followed for certain operations. [CVE-2016-2178] In a DTLS connection where handshake messages are delivered out-of-order those messages that OpenSSL is not yet ready to process will be buffered for later use. Under certain circumstances, a flaw in the logic means that those messages do not get removed from the buffer even though the handshake has been completed. An attacker could force up to approx. 15 messages to remain in the buffer when they are no longer required. These messages will be cleared when the DTLS connection is closed. The default maximum size for a message is 100k. Therefore the attacker could force an additional 1500k to be consumed per connection. [CVE-2016-2179] A flaw in the DTLS replay attack protection mechanism means that records that arrive for future epochs update the replay protection "window" before the MAC for the record has been validated. This could be exploited by an attacker by sending a record for the next epoch (which does not have to decrypt or have a valid MAC), with a very large sequence number. This means that all subsequent legitimate packets are dropped causing a denial of service for a specific DTLS connection. [CVE-2016-2181] In OpenSSL 1.0.2 and earlier some missing message length checks can result in OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical DoS risk but this has not been observed in practice on common platforms. [CVE-2016-6306] III. Impact A remote attacker can cause OpenSSL server, regardless whether OCSP is supported, to have unbounded memory growth, and eventually lead to a Denial of Service. [CVE-2016-6304] If an attacker is able to supply very large amounts of input data after a previous call to EVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. [CVE-2016-6303] An attacker who can send a malformed ticket to the server can cause an OOB read which will ultimately lead to a crash, resulting in a Denial of Service. [CVE-2016-6302] A local attacker can cause an application that parses overly large certificate or CRL to crash. TLS is not affected. [CVE-2016-2182] A local attacker who can create a specially-crafted time stamp file and pass it through the "ts" command of openssl(1) can cause it to crash. This functionality is not used by the SSL/TLS implementation. [CVE-2016-2180] Some OpenSSL code is questionable to integer overflow, which may lead to heap corruption. [CVE-2016-2177] An attacker may recover the private DSA key by conducting timing attack. [CVE-2016-2178] A remote attacker may cause a DTLS server to exhaust memory, resulting in a Denial of Service. [CVE-2016-2179] A remote attacker who can send DTLS records can cause the server to drop all subsequent packets for a specific connection. [CVE-2016-2181] A remote attacker can, in theory, cause OOB reads if the server enabled client authentication. [CVE-2016-6306] IV. Workaround No workaround is available. V. Solution Perform one of the following: 1) Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date. Restart all daemons that use the library, or reboot the system. 2) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install Restart all daemons that use the library, or reboot the system. 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. [FreeBSD 10.3] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.3.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.3.patch.asc # gpg --verify openssl-10.3.patch.asc [FreeBSD 10.1 and 10.2] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.2.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-10.2.patch.as # gpg --verify openssl-10.2.patch.asc [FreeBSD 9.3] # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-9.3.patch # fetch https://security.FreeBSD.org/patches/SA-16:26/openssl-9.3.patch.as # gpg --verify openssl-9.3.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile the operating system using buildworld and installworld as described in . Restart all daemons that use the library, or reboot the system. VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision ------------------------------------------------------------------------- stable/9/ r306229 releng/9.3/ r206230 stable/10/ r306196 releng/10.1/ r206230 releng/10.2/ r206230 releng/10.3/ r206230 stable/11/ r306195 releng/11.0/ r306198 ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at _______________________________________________ freebsd-security-notifications em freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications To unsubscribe, send any mail to "freebsd-security-notifications-unsubscribe em freebsd.org" ----- End forwarded message ----- From security em unicamp.br Wed Sep 28 07:41:03 2016 From: security em unicamp.br (CSIRT - UNICAMP) Date: Wed, 28 Sep 2016 10:41:03 -0000 Subject: [SECURITY-L] [USN-3088-1] Bind vulnerability Message-ID: <20160928104102.GI18685@unicamp.br> ----- Forwarded message from Marc Deslauriers ----- Date: Tue, 27 Sep 2016 14:08:21 -0400 From: Marc Deslauriers To: ubuntu-security-announce em lists.ubuntu.com Subject: [USN-3088-1] Bind vulnerability ========================================================================== Ubuntu Security Notice USN-3088-1 September 27, 2016 bind9 vulnerability ========================================================================== A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 16.04 LTS - Ubuntu 14.04 LTS - Ubuntu 12.04 LTS Summary: Bind could be made to crash if it received specially crafted network traffic. Software Description: - bind9: Internet Domain Name Server Details: It was discovered that Bind incorrectly handled building responses to certain specially crafted requests. A remote attacker could possibly use this issue to cause Bind to crash, resulting in a denial of service. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 16.04 LTS: bind9 1:9.10.3.dfsg.P4-8ubuntu1.1 Ubuntu 14.04 LTS: bind9 1:9.9.5.dfsg-3ubuntu0.9 Ubuntu 12.04 LTS: bind9 1:9.8.1.dfsg.P1-4ubuntu0.17 In general, a standard system update will make all the necessary changes. References: http://www.ubuntu.com/usn/usn-3088-1 CVE-2016-2776 Package Information: https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-8ubuntu1.1 https://launchpad.net/ubuntu/+source/bind9/1:9.9.5.dfsg-3ubuntu0.9 https://launchpad.net/ubuntu/+source/bind9/1:9.8.1.dfsg.P1-4ubuntu0.17 -- ubuntu-security-announce mailing list ubuntu-security-announce em lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce ----- End forwarded message -----