svn commit: r438952 - head/security/vuxml

Thu Apr 20 14:25:25 UTC 2017

Author: sunpoet
Date: Thu Apr 20 14:25:23 2017
New Revision: 438952
URL: https://svnweb.freebsd.org/changeset/ports/438952

Log:
  Document cURL vulnerability

Modified:
  head/security/vuxml/vuln.xml

Modified: head/security/vuxml/vuln.xml
==============================================================================

--- head/security/vuxml/vuln.xml	Thu Apr 20 14:20:30 2017	(r438951)
+++ head/security/vuxml/vuln.xml	Thu Apr 20 14:25:23 2017	(r438952)
@@ -58,6 +58,42 @@ Notes:
   * Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
 -->
 <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+  <vuln vid="3e2e9b44-25ce-11e7-a175-939b30e0836d">
+    <topic>cURL -- TLS session resumption client cert bypass (again)</topic>
+    <affects>
+      <package>
+	<name>curl</name>
+	<range><ge>7.52.0</ge><lt>7.54.0</lt></range>
+      </package>
+    </affects>
+    <description>
+      <body xmlns="http://www.w3.org/1999/xhtml">
+	<p>cURL security advisory:</p>
+	<blockquote cite="https://curl.haxx.se/docs/adv_20170419.html">
+	  <p>libcurl would attempt to resume a TLS session even if the client
+	    certificate had changed. That is unacceptable since a server by
+	    specification is allowed to skip the client certificate check on
+	    resume, and may instead use the old identity which was established
+	    by the previous certificate (or no certificate).</p>
+	  <p>libcurl supports by default the use of TLS session id/ticket to
+	    resume previous TLS sessions to speed up subsequent TLS handshakes.
+	    They are used when for any reason an existing TLS connection
+	    couldn't be kept alive to make the next handshake faster.</p>
+	  <p>This flaw is a regression and identical to CVE-2016-5419 reported
+	    on August 3rd 2016, but affecting a different version range.</p>
+	</blockquote>
+      </body>
+    </description>
+    <references>
+      <cvename>CVE-2017-7468</cvename>
+      <url>https://curl.haxx.se/docs/adv_20170419.html</url>
+    </references>
+    <dates>
+      <discovery>2017-04-19</discovery>
+      <entry>2017-04-20</entry>
+    </dates>
+  </vuln>
+
   <vuln vid="cf133acc-82e7-4755-a66a-5ddf90dacbe6">
     <topic>graphite2 -- out-of-bounds write with malicious font</topic>
     <affects>
