- Arch-security - lists.archlinux.org

[arch-security] [ASA-201609-28] lib32-openssl: denial of service
by Levente Polyak 27 Sep '16

27 Sep '16

Arch Linux Security Advisory ASA-201609-28 ========================================== Severity: Medium Date : 2016-09-27 CVE-ID : CVE-2016-7052 Package : lib32-openssl Type : denial of service Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package lib32-openssl before version 1:1.0.2.j-1 is vulnerable to denial of service. Resolution ========== Upgrade to 1:1.0.2.j-1. # pacman -Syu "lib32-openssl>=1:1.0.2.j-1" The problem has been fixed upstream in version 1.0.2.j. Workaround ========== None. Description =========== A bug fix which included a CRL sanity check was added to OpenSSL 1.1.0 but was omitted from OpenSSL 1.0.2i. As a result any attempt to use CRLs in OpenSSL 1.0.2i will crash with a null pointer exception. The issue was reported to OpenSSL on 22nd September 2016 by Bruce Stephens and Thomas Jakobi. Impact ====== A remote attacker is able to perform a denial of service attack by using a certificate revocation list. References ========== https://www.openssl.org/news/secadv/20160926.txt https://access.redhat.com/security/cve/CVE-2016-7052

1 0

[arch-security] [ASA-201609-27] wireshark-cli: denial of service
by Levente Polyak 26 Sep '16

26 Sep '16

Arch Linux Security Advisory ASA-201609-27 ========================================== Severity: Medium Date : 2016-09-26 CVE-ID : CVE-2016-7175 CVE-2016-7176 CVE-2016-7177 CVE-2016-7178 CVE-2016-7179 CVE-2016-7180 Package : wireshark-cli Type : denial of service Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package wireshark-cli before version 2.2.0-2 is vulnerable to denial of service. Resolution ========== Upgrade to 2.2.0-2. # pacman -Syu "wireshark-cli>=2.2.0-2" The problems have been fixed upstream in version 2.2.0. Workaround ========== None. Description =========== - CVE-2016-7175 (denial of service) It may be possible to make Wireshark crash via the QNX6 QNET dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. - CVE-2016-7176 (denial of service) It may be possible to make Wireshark crash via the H.225 dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. - CVE-2016-7177 (denial of service) It may be possible to make Wireshark crash via the Catapult DCT2000 dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. - CVE-2016-7178 (denial of service) It may be possible to make Wireshark crash via the UMTS FP dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. - CVE-2016-7179 (denial of service) It may be possible to make Wireshark crash via the Catapult DCT2000 dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. - CVE-2016-7180 (denial of service) It may be possible to make Wireshark crash via the IPMI Trace dissector by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. Impact ====== A remote attacker is able use specially crafted packets to perform a denial of service attack via various vectors. References ========== https://www.wireshark.org/security/wnpa-sec-2016-50.html https://www.wireshark.org/security/wnpa-sec-2016-51.html https://www.wireshark.org/security/wnpa-sec-2016-52.html https://www.wireshark.org/security/wnpa-sec-2016-53.html https://www.wireshark.org/security/wnpa-sec-2016-54.html https://www.wireshark.org/security/wnpa-sec-2016-55.html https://access.redhat.com/security/cve/CVE-2016-7175 https://access.redhat.com/security/cve/CVE-2016-7176 https://access.redhat.com/security/cve/CVE-2016-7177 https://access.redhat.com/security/cve/CVE-2016-7178 https://access.redhat.com/security/cve/CVE-2016-7179 https://access.redhat.com/security/cve/CVE-2016-7180

1 0

[arch-security] [ASA-201609-26] lib32-gnutls: certificate verification bypass
by Levente Polyak 26 Sep '16

26 Sep '16

Arch Linux Security Advisory ASA-201609-26 ========================================== Severity: Medium Date : 2016-09-26 CVE-ID : CVE-2016-7444 Package : lib32-gnutls Type : certificate verification bypass Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package lib32-gnutls before version 3.4.15-1 is vulnerable to certificate verification bypass. Resolution ========== Upgrade to 3.4.15-1. # pacman -Syu "lib32-gnutls>=3.4.15-1" The problem has been fixed upstream in version 3.4.15. Workaround ========== None. Description =========== Incorrect length validation on gnutls's gnutls_ocsp_resp_check_crt method can allow an attacker to use a OCSP response for a different certificate (but from the same CA) to continue using a revoked certificate. This can happen if the serial from the revoked certificate is a prefix of the other one, and the additional bytes happen to be equal on the system doing the verification. Impact ====== A remote attacker is able to bypass certificate verification and continue using a revoked certificate under certain circumstances. References ========== https://lists.gnupg.org/pipermail/gnutls-devel/2016-September/008146.html https://gitlab.com/gnutls/gnutls/commit/964632f37dfdfb914ebc5e49db4fa29af35… https://access.redhat.com/security/cve/CVE-2016-7444

1 0

[arch-security] [ASA-201609-25] gnutls: certificate verification bypass
by Levente Polyak 26 Sep '16

26 Sep '16

Arch Linux Security Advisory ASA-201609-25 ========================================== Severity: Medium Date : 2016-09-26 CVE-ID : CVE-2016-7444 Package : gnutls Type : certificate verification bypass Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package gnutls before version 3.4.15-1 is vulnerable to certificate verification bypass. Resolution ========== Upgrade to 3.4.15-1. # pacman -Syu "gnutls>=3.4.15-1" The problem has been fixed upstream in version 3.4.15. Workaround ========== None. Description =========== Incorrect length validation on gnutls's gnutls_ocsp_resp_check_crt method can allow an attacker to use a OCSP response for a different certificate (but from the same CA) to continue using a revoked certificate. This can happen if the serial from the revoked certificate is a prefix of the other one, and the additional bytes happen to be equal on the system doing the verification. Impact ====== A remote attacker is able to bypass certificate verification and continue using a revoked certificate under certain circumstances. References ========== https://lists.gnupg.org/pipermail/gnutls-devel/2016-September/008146.html https://gitlab.com/gnutls/gnutls/commit/964632f37dfdfb914ebc5e49db4fa29af35… https://access.redhat.com/security/cve/CVE-2016-7444

1 0

[arch-security] [ASA-201609-24] lib32-openssl: multiple issues
by Levente Polyak 26 Sep '16

26 Sep '16

Arch Linux Security Advisory ASA-201609-24 ========================================== Severity: High Date : 2016-09-26 CVE-ID : CVE-2016-6304 CVE-2016-2178 CVE-2016-2177 CVE-2016-2183 CVE-2016-2182 CVE-2016-6303 CVE-2016-2179 CVE-2016-2180 CVE-2016-2181 CVE-2016-6302 CVE-2016-6306 Package : lib32-openssl Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package lib32-openssl before version 1:1.0.2.i-1 is vulnerable to multiple issues including denial of service, private key recovery, information disclosure and arbitrary code execution. Resolution ========== Upgrade to 1:1.0.2.i-1. # pacman -Syu "lib32-openssl>=1:1.0.2.i-1" The problems have been fixed upstream in version 1.0.2.i. Workaround ========== None. Description =========== - CVE-2016-6304 (denial of service) 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. This will eventually lead to a Denial Of Service attack through memory exhaustion. Servers with a default configuration are vulnerable even if they do not support OCSP. Builds using the "no-ocsp" build time option are not affected. - CVE-2016-2178 (private key recovery) 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. This has been demonstrated through a cache-timing attack to be sufficient for an attacker to recover the private DSA key. - CVE-2016-2177 (denial of service) OpenSSL through 1.0.2h incorrectly uses pointer arithmetic for heap- buffer boundary checks, which might allow remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact by leveraging unexpected malloc behavior, related to s3_srvr.c, ssl_sess.c, and t1_lib.c. - CVE-2016-2183 (information disclosure) SWEET32 (https://sweet32.info) is an attack on older block cipher algorithms that use a block size of 64 bits. In mitigation for the SWEET32 attack DES based ciphersuites have been moved from the HIGH cipherstring group to MEDIUM. - CVE-2016-2182 (arbitrary code execution) 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-6303 (arbitrary code execution) 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 t MVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. The amount of data needed is comparable to SIZE_MAX which is impractical on most platforms. - CVE-2016-2179 (denial of service) 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. By opening many simultaneous connections an attacker could cause a DoS attack through memory exhaustion. - CVE-2016-2180 (denial of service) 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-2181 (denial of service) 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-6302 (denial of service) 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. The use of SHA512 in TLS session tickets is comparatively rare as it requires a custom server callback and ticket lookup mechanism. - CVE-2016-6306 (denial of service) 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. The messages affected are client certificate, client certificate request and server certificate. As a result the attack can only be performed against a client or a server which enables client authentication. Impact ====== A remote attacker is able to execute arbitrary code, recovery private keys, disclose sensitive information or perform a denial of service attack via various vectors. References ========== https://www.openssl.org/news/secadv/20160922.txt https://access.redhat.com/security/cve/CVE-2016-6304 https://access.redhat.com/security/cve/CVE-2016-2178 https://access.redhat.com/security/cve/CVE-2016-2177 https://access.redhat.com/security/cve/CVE-2016-2183 https://access.redhat.com/security/cve/CVE-2016-2182 https://access.redhat.com/security/cve/CVE-2016-6303 https://access.redhat.com/security/cve/CVE-2016-2179 https://access.redhat.com/security/cve/CVE-2016-2180 https://access.redhat.com/security/cve/CVE-2016-2181 https://access.redhat.com/security/cve/CVE-2016-6302 https://access.redhat.com/security/cve/CVE-2016-6306

1 0

[arch-security] [ASA-201609-23] openssl: multiple issues
by Levente Polyak 26 Sep '16

26 Sep '16

Arch Linux Security Advisory ASA-201609-23 ========================================== Severity: High Date : 2016-09-26 CVE-ID : CVE-2016-6304 CVE-2016-2178 CVE-2016-2177 CVE-2016-2183 CVE-2016-2182 CVE-2016-6303 CVE-2016-2179 CVE-2016-2180 CVE-2016-2181 CVE-2016-6302 CVE-2016-6306 Package : openssl Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package openssl before version 1.0.2.i-1 is vulnerable to multiple issues including denial of service, private key recovery, information disclosure and arbitrary code execution. Resolution ========== Upgrade to 1.0.2.i-1. # pacman -Syu "openssl>=1.0.2.i-1" The problems have been fixed upstream in version 1.0.2.i. Workaround ========== None. Description =========== - CVE-2016-6304 (denial of service) 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. This will eventually lead to a Denial Of Service attack through memory exhaustion. Servers with a default configuration are vulnerable even if they do not support OCSP. Builds using the "no-ocsp" build time option are not affected. - CVE-2016-2178 (private key recovery) 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. This has been demonstrated through a cache-timing attack to be sufficient for an attacker to recover the private DSA key. - CVE-2016-2177 (denial of service) OpenSSL through 1.0.2h incorrectly uses pointer arithmetic for heap- buffer boundary checks, which might allow remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact by leveraging unexpected malloc behavior, related to s3_srvr.c, ssl_sess.c, and t1_lib.c. - CVE-2016-2183 (information disclosure) SWEET32 (https://sweet32.info) is an attack on older block cipher algorithms that use a block size of 64 bits. In mitigation for the SWEET32 attack DES based ciphersuites have been moved from the HIGH cipherstring group to MEDIUM. - CVE-2016-2182 (arbitrary code execution) 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-6303 (arbitrary code execution) 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 t MVP_EncryptUpdate() with a partial block then a length check can overflow resulting in a heap corruption. The amount of data needed is comparable to SIZE_MAX which is impractical on most platforms. - CVE-2016-2179 (denial of service) 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. By opening many simultaneous connections an attacker could cause a DoS attack through memory exhaustion. - CVE-2016-2180 (denial of service) 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-2181 (denial of service) 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-6302 (denial of service) 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. The use of SHA512 in TLS session tickets is comparatively rare as it requires a custom server callback and ticket lookup mechanism. - CVE-2016-6306 (denial of service) 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. The messages affected are client certificate, client certificate request and server certificate. As a result the attack can only be performed against a client or a server which enables client authentication. Impact ====== A remote attacker is able to execute arbitrary code, recovery private keys, disclose sensitive information or perform a denial of service attack via various vectors. References ========== https://www.openssl.org/news/secadv/20160922.txt https://access.redhat.com/security/cve/CVE-2016-6304 https://access.redhat.com/security/cve/CVE-2016-2178 https://access.redhat.com/security/cve/CVE-2016-2177 https://access.redhat.com/security/cve/CVE-2016-2183 https://access.redhat.com/security/cve/CVE-2016-2182 https://access.redhat.com/security/cve/CVE-2016-6303 https://access.redhat.com/security/cve/CVE-2016-2179 https://access.redhat.com/security/cve/CVE-2016-2180 https://access.redhat.com/security/cve/CVE-2016-2181 https://access.redhat.com/security/cve/CVE-2016-6302 https://access.redhat.com/security/cve/CVE-2016-6306

1 0

[arch-security] [ASA-201609-22] firefox: multiple issues
by Levente Polyak 22 Sep '16

22 Sep '16

Arch Linux Security Advisory ASA-201609-22 ========================================== Severity: Critical Date : 2016-09-22 CVE-ID : CVE-2016-5256 CVE-2016-5257 CVE-2016-5270 CVE-2016-5271 CVE-2016-5272 CVE-2016-5273 CVE-2016-5274 CVE-2016-5275 CVE-2016-5276 CVE-2016-5277 CVE-2016-5278 CVE-2016-5279 CVE-2016-5280 CVE-2016-5281 CVE-2016-5282 CVE-2016-5283 CVE-2016-5284 Package : firefox Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package firefox before version 49.0-1 is vulnerable to multiple issues including but not limited to arbitrary code execution, information disclosure and certificate verification bypass. Resolution ========== Upgrade to 49.0-1. # pacman -Syu "firefox>=49.0-1" The problems have been fixed upstream in version 49.0. Workaround ========== None. Description =========== - CVE-2016-5256 (arbitrary code execution) Mozilla developers Christoph Diehl, Christian Holler, Gary Kwong, Nathan Froyd, Honza Bambas, Seth Fowler, and Michael Smith reported memory safety bugs present in Firefox 48. Some of these bugs showed evidence of memory corruption under certain circumstances could potentially exploited to run arbitrary code. - CVE-2016-5257 (arbitrary code execution) Mozilla developers and community members Christoph Diehl, Andrew McCreight, Dan Minor, Byron Campen, Jon Coppeard, Steve Fink, Tyson Smith, Philipp, and Carsten Book reported memory safety bugs present in Firefox 48 and Firefox ESR 45.3. Some of these bugs showed evidence of memory corruption and we presume that with enough effort at least some of these could be exploited to run arbitrary code. - CVE-2016-5270 (arbitrary code execution) An out-of-bounds write of a boolean value during text conversion with some unicode characters. - CVE-2016-5271 (information disclosure) An out-of-bounds read during the processing of text runs in some pages using display:contents. - CVE-2016-5272 (arbitrary code execution) A bad cast when processing layout with input elements can result in a potentially exploitable crash. - CVE-2016-5273 (arbitrary code execution) A potentially exploitable crash in accessibility in the mozilla::a11y::HyperTextAccessible::GetChildOffset function. - CVE-2016-5274 (arbitrary code execution) A use-after-free vulnerability has been discovered in the nsFrameManager::CaptureFrameState function in web animations during restyling. - CVE-2016-5275 (arbitrary code execution) A buffer overflow vulnerability has been discovered in the mozilla::gfx::FilterSupport::ComputeSourceNeededRegions function when working with empty filters during canvas rendering. - CVE-2016-5276 (arbitrary code execution) A use-after-free vulnerability has been discovered in the mozilla::a11y::DocAccessible::ProcessInvalidationList function triggered by setting a aria-owns attribute. - CVE-2016-5277 (arbitrary code execution) A user-after-free vulnerability has been disconvered in the nsRefreshDriver::Tick function with web animations when destroying a timeline. - CVE-2016-5278 (arbitrary code execution) A potentially exploitable crash caused by a heap based buffer overflow has been discovered in the nsBMPEncoder::AddImageFrame function while encoding image frames to images. - CVE-2016-5279 (information disclosure) The full path to local files is available to scripts when local files are drag and dropped into Firefox. - CVE-2016-5280 (arbitrary code execution) A use-after-free vulnerability has been discovered in the mozilla::nsTextNodeDirectionalityMap::RemoveElementFromMap function when changing text direction. - CVE-2016-5281 (arbitrary code execution) A use-after-free vulnerability has been discovered in the DOMSVGLength when manipulating SVG format content through a script. - CVE-2016-5282 (access restriction bypass) Favicons can be loaded through non-whitelisted protocols, such as jar. - CVE-2016-5283 (information disclosure) A timing attack vulnerability was discovered using iframes to potentially reveal private cross-origin data using document resizes and link colors. - CVE-2016-5284 (certificate verification bypass) Due to flaws in the process used to update "Preloaded Public Key Pinning", the pinning for add-on updates became ineffective in early September. An attacker who was able to get a mis-issued certificate for a Mozilla web site could send malicious add-on updates to users on networks controlled by the attacker. Users who have not installed any add-ons are not affected. Impact ====== A remote attacker is able to execute arbitrary code, disclose sensitive information and bypass certificate verification via various vectors. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2016-85/ https://access.redhat.com/security/cve/CVE-2016-5256 https://access.redhat.com/security/cve/CVE-2016-5257 https://access.redhat.com/security/cve/CVE-2016-5270 https://access.redhat.com/security/cve/CVE-2016-5271 https://access.redhat.com/security/cve/CVE-2016-5272 https://access.redhat.com/security/cve/CVE-2016-5273 https://access.redhat.com/security/cve/CVE-2016-5274 https://access.redhat.com/security/cve/CVE-2016-5275 https://access.redhat.com/security/cve/CVE-2016-5276 https://access.redhat.com/security/cve/CVE-2016-5277 https://access.redhat.com/security/cve/CVE-2016-5278 https://access.redhat.com/security/cve/CVE-2016-5279 https://access.redhat.com/security/cve/CVE-2016-5280 https://access.redhat.com/security/cve/CVE-2016-5281 https://access.redhat.com/security/cve/CVE-2016-5282 https://access.redhat.com/security/cve/CVE-2016-5283 https://access.redhat.com/security/cve/CVE-2016-5284

1 0

[arch-security] [ASA-201609-21] tomcat7: proxy injection
by Levente Polyak 22 Sep '16

22 Sep '16

Arch Linux Security Advisory ASA-201609-21 ========================================== Severity: Medium Date : 2016-09-22 CVE-ID : CVE-2016-5388 Package : tomcat7 Type : proxy injection Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package tomcat7 before version 7.0.72-1 is vulnerable to proxy injection. Resolution ========== Upgrade to 7.0.72-1. # pacman -Syu "tomcat7>=7.0.72-1" The problems have been fixed upstream in version 7.0.72. Workaround ========== None. Description =========== It was discovered that tomcat used the value of the Proxy header from HTTP requests to initialize the HTTP_PROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. Impact ====== A remote attacker is able to use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. References ========== https://access.redhat.com/security/cve/CVE-2016-5388 https://www.apache.org/security/asf-httpoxy-response.txt

1 0

[arch-security] [ASA-201609-20] irssi: arbitrary code execution
by Jelle van der Waa 22 Sep '16

22 Sep '16

Arch Linux Security Advisory ASA-201609-20 ========================================== Severity: High Date : 2016-09-22 CVE-ID : CVE-2016-7045 Package : irssi Type : arbitrary code execution Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package irssi before version 0.8.20-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 0.8.20-1. # pacman -Syu "irssi>=0.8.20-1" The problem has been fixed upstream in version 0.8.20. Workaround ========== None. Description =========== The format_send_to_gui() function does not validate the length of the string before incrementing the `ptr' pointer in all cases. If that happens, the pointer `ptr' can be incremented twice and thus end past the boundaries of the original `dup' buffer. Remote code execution might be difficult since only Nuls are written. Impact ====== A remote attacker can perform a denial of service attack or possibly execute arbitrary code on the affected host. References ========== https://irssi.org/security/irssi_sa_2016.txt http://www.openwall.com/lists/oss-security/2016/09/21/11 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7045

1 0

[arch-security] [ASA-201609-19] curl: denial of service
by Jelle van der Waa 20 Sep '16

20 Sep '16

Arch Linux Security Advisory ASA-201609-19 ========================================== Severity: Low Date : 20916-09-20 CVE-ID : CVE-2016-7167 Package : curl Type : denial of service Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package curl before version 7.50.3-1 is vulnerable to denial of service. Resolution ========== Upgrade to 7.50.3-1. # pacman -Syu "curl>=7.50.3-1" The problem has been fixed upstream in version 7.50.3. Workaround ========== None. Description =========== The four libcurl functions `curl_escape()`, `curl_easy_escape()`, `curl_unescape` and `curl_easy_unescape` perform string URL percent escaping and unescaping. They accept custom string length inputs in signed integer arguments. (The functions having names without "easy" being the deprecated versions of the others.) The provided string length arguments were not properly checked and due to arithmetic in the functions, passing in the length 0xffffffff (2^32-1 or `UINT_MAX` or even just -1) would end up causing an allocation of zero bytes of heap memory that curl would attempt to write gigabytes of data into. The use of 'int' for this input type in the API is of course unwise but has remained so in order to maintain the API over the years. We are not aware of any exploit of this flaw. Impact ====== A remote attacker might cause a crash by providing a specially crafted URL, leading to a denial of service. References ========== http://www.openwall.com/lists/oss-security/2016/09/14/1 https://curl.haxx.se/docs/adv_20160914.html https://access.redhat.com/security/cve/CVE-2016-7167

1 0