summaryrefslogtreecommitdiff
path: root/security/vuxml/vuln.xml
diff options
context:
space:
mode:
Diffstat (limited to 'security/vuxml/vuln.xml')
-rw-r--r--security/vuxml/vuln.xml32
1 files changed, 32 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index 68f2910a0bd0..adca21846b35 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -58,6 +58,38 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="24673ed7-2bf3-11e7-b291-b499baebfeaf">
+ <topic>LibreSSL -- TLS verification vulnerability</topic>
+ <affects>
+ <package>
+ <name>libressl</name>
+ <range><ge>2.5.1</ge><lt>2.5.3_1</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p> Jakub Jirutka reports:</p>
+ <blockquote cite="http://seclists.org/oss-sec/2017/q2/145">
+ <p>LibreSSL 2.5.1 to 2.5.3 lacks TLS certificate verification if
+ SSL_get_verify_result is relied upon for a later check of a
+ verification result, in a use case where a user-provided verification
+ callback returns 1, as demonstrated by acceptance of invalid
+ certificates by nginx.
+ </p>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <url>http://seclists.org/oss-sec/2017/q2/145</url>
+ <url>https://github.com/libressl-portable/portable/issues/307</url>
+ <cvename>CVE-2017-8301</cvename>
+ </references>
+ <dates>
+ <discovery>2017-04-27</discovery>
+ <entry>2017-04-28</entry>
+ </dates>
+ </vuln>
+
<vuln vid="631c4710-9be5-4a80-9310-eb2847fe24dd">
<topic>jenkins -- multiple vulnerabilities</topic>
<affects>