|Summary:||<dev-libs/openssl-1.0.2k: Multiple vulnerabilities|
|Product:||Gentoo Security||Reporter:||Thomas Deutschmann <whissi>|
|Component:||Vulnerabilities||Assignee:||Gentoo Security <security>|
|Whiteboard:||A3 [glsa cve]|
|Runtime testing required:||---|
Description Thomas Deutschmann 2017-01-26 16:10:31 UTC
OpenSSL Security Advisory [26 Jan 2017] ======================================== Truncated packet could crash via OOB read (CVE-2017-3731) ========================================================= Severity: Moderate If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k This issue was reported to OpenSSL on 13th November 2016 by Robert Święcki of Google. The fix was developed by Andy Polyakov of the OpenSSL development team. Bad (EC)DHE parameters cause a client crash (CVE-2017-3730) =========================================================== Severity: Moderate If a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attack. OpenSSL 1.1.0 users should upgrade to 1.1.0d This issue does not affect OpenSSL version 1.0.2. Note that this issue was fixed prior to it being recognised as a security concern. This means the git commit with the fix does not contain the CVE identifier. The relevant fix commit can be identified by commit hash efbe126e3. This issue was reported to OpenSSL on 14th January 2017 by Guido Vranken. The fix was developed by Matt Caswell of the OpenSSL development team. BN_mod_exp may produce incorrect results on x86_64 (CVE-2017-3732) ================================================================== Severity: Moderate There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem. OpenSSL 1.1.0 users should upgrade to 1.1.0d OpenSSL 1.0.2 users should upgrade to 1.0.2k This issue was reported to OpenSSL on 15th January 2017 by the OSS-Fuzz project. The fix was developed by Andy Polyakov of the OpenSSL development team. Montgomery multiplication may produce incorrect results (CVE-2016-7055) ======================================================================= Severity: Low This issue was previously fixed in 1.1.0c and covered in security advisory https://www.openssl.org/news/secadv/20161110.txt OpenSSL 1.0.2k users should upgrade to 1.0.2k Note ==== Support for version 1.0.1 ended on 31st December 2016. Support for versions 0.9.8 and 1.0.0 ended on 31st December 2015. Those versions are no longer receiving security updates. References ========== URL for this Security Advisory: https://www.openssl.org/news/secadv/20170126.txt Note: the online version of the advisory may be updated with additional details over time. For details of OpenSSL severity classifications please see: https://www.openssl.org/policies/secpolicy.html
Comment 1 Lars Wendler (Polynomial-C) 2017-01-26 16:13:42 UTC
commit 8607ecd9f9693a05df6f8ef5f0e2b49076998079 Author: Lars Wendler <email@example.com> Date: Thu Jan 26 17:11:08 2017 dev-libs/openssl: Sec bump to versions 1.0.2k and 1.1.0d (bug #607318). Package-Manager: Portage-2.3.3, Repoman-2.3.1 Arches please test and mark stable =dev-libs/openssl-1.0.2k with target KEYWORDS: alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd ~arm-linux ~x86-linux
Comment 2 Jeroen Roovers 2017-01-26 17:39:29 UTC
Stable for HPPA.
Comment 3 Agostino Sarubbo 2017-01-27 09:02:38 UTC
Comment 4 Agostino Sarubbo 2017-01-27 09:07:50 UTC
Comment 5 Tobias Klausmann 2017-01-27 13:24:43 UTC
Stable on alpha.
Comment 7 Markus Meier 2017-02-12 20:10:23 UTC
Comment 8 Thomas Deutschmann 2017-02-13 01:28:15 UTC
New GLSA request filed.
Comment 9 GLSAMaker/CVETool Bot 2017-02-14 12:43:02 UTC
This issue was resolved and addressed in GLSA 201702-07 at https://security.gentoo.org/glsa/201702-07 by GLSA coordinator Thomas Deutschmann (whissi).
Comment 10 Thomas Deutschmann 2017-02-14 12:44:44 UTC
Re-opening for remaining arches.
Comment 11 Agostino Sarubbo 2017-02-17 10:59:18 UTC
Comment 12 Agostino Sarubbo 2017-02-18 14:46:37 UTC
ia64 stable. Maintainer(s), please cleanup.
Comment 13 Lars Wendler (Polynomial-C) 2017-02-18 16:59:07 UTC
commit a9964d9ed27ad30312a1fd26d8a4f56b67b9f876 Author: Lars Wendler <firstname.lastname@example.org> Date: Sat Feb 18 17:46:27 2017 dev-libs/openssl: Security cleanup (bug #607318). Package-Manager: Portage-2.3.3, Repoman-2.3.1
Comment 14 Thomas Deutschmann 2017-02-21 20:34:51 UTC
Repository is clean, GLSA is published, all done.