Date: Thu, 7 Dec 2017 15:47:32 +0000 (UTC) From: Bernard Spil <brnrd@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r455705 - head/security/vuxml Message-ID: <201712071547.vB7FlWsg082669@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: brnrd Date: Thu Dec 7 15:47:32 2017 New Revision: 455705 URL: https://svnweb.freebsd.org/changeset/ports/455705 Log: secuirty/vuxml: Document OpenSSL vulnerabilities Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Dec 7 15:45:00 2017 (r455704) +++ head/security/vuxml/vuln.xml Thu Dec 7 15:47:32 2017 (r455705) @@ -58,6 +58,59 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">; + <vuln vid="3bb451fc-db64-11e7-ac58-b499baebfeaf"> + <topic>OpenSSL -- multiple vulnerabilities</topic> + <affects> + <package> + <name>openssl</name> + <range><gt>1.0.2</gt><lt>1.0.2n</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>The OpenSSL project reports:</p> + <blockquote cite="https://www.openssl.org/news/secadv/20171207.txt">; + <ul><li>Read/write after SSL object in error state (CVE-2017-3737)<br/> + OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error + state" mechanism. The intent was that if a fatal error occurred + during a handshake then OpenSSL would move into the error state and + would immediately fail if you attempted to continue the handshake. + This works as designed for the explicit handshake functions + (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to + a bug it does not work correctly if SSL_read() or SSL_write() is + called directly. In that scenario, if the handshake fails then a + fatal error will be returned in the initial function call. If + SSL_read()/SSL_write() is subsequently called by the application for + the same SSL object then it will succeed and the data is passed + without being decrypted/encrypted directly from the SSL/TLS record + layer.</li> + <li>rsaz_1024_mul_avx2 overflow bug on x86_64 (CVE-2017-3738)<br/> + There is an overflow bug in the AVX2 Montgomery multiplication + procedure used in exponentiation with 1024-bit moduli. 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 DH1024 are + considered just feasible, 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 + significant. However, for an attack on TLS to be meaningful, the + server would have to share the DH1024 private key among multiple + clients, which is no longer an option since CVE-2016-0701.</li> + </ul> + </blockquote> + </body> + </description> + <references> + <url>https://www.openssl.org/news/secadv/20171207.txt</url>; + <cvename>CVE-2017-3737</cvename> + <cvename>CVE-2017-3738</cvename> + </references> + <dates> + <discovery>2017-12-07</discovery> + <entry>2017-12-07</entry> + </dates> + </vuln> + <vuln vid="9442a811-dab3-11e7-b5af-a4badb2f4699"> <topic>FreeBSD -- OpenSSL multiple vulnerabilities</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201712071547.vB7FlWsg082669>