svn commit: r481849 - head/security/vuxml

Thu Oct 11 19:54:19 UTC 2018

Author: thierry
Date: Thu Oct 11 19:54:18 2018
New Revision: 481849
URL: https://svnweb.freebsd.org/changeset/ports/481849

Log:
  Add an entry for a memory leak bug in net-im/tox < v0.2.8.

Modified:
  head/security/vuxml/vuln.xml

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

--- head/security/vuxml/vuln.xml	Thu Oct 11 19:50:57 2018	(r481848)
+++ head/security/vuxml/vuln.xml	Thu Oct 11 19:54:18 2018	(r481849)
@@ -58,6 +58,35 @@ Notes:
   * Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
 -->
 <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+  <vuln vid="4c11b51e-cd8d-11e8-b0cb-a0f3c100ae18">
+    <topic>Memory leak bug in Toxcore</topic>
+    <affects>
+      <package>
+	<name>toxcore</name>
+	<range><lt>0.2.8,1</lt></range>
+      </package>
+    </affects>
+    <description>
+      <body xmlns="http://www.w3.org/1999/xhtml">
+	<p>The Tox project blog reports:</p>
+	<blockquote cite="https://blog.tox.chat/2018/10/memory-leak-bug-and-new-toxcore-release-fixing-it/">
+	  <p>A memory leak bug was discovered in Toxcore that can be triggered remotely to
+exhaust one’s system memory, resulting in a denial of service attack.
+The bug is present in the TCP Server module of Toxcore and therefore it
+affects mostly bootstrap nodes. Regular Tox clients generally have the
+TCP Server functionality disabled by default, leaving them unaffected.</p>
+	</blockquote>
+      </body>
+    </description>
+    <references>
+      <url>https://blog.tox.chat/2018/10/memory-leak-bug-and-new-toxcore-release-fixing-it/</url>
+    </references>
+    <dates>
+      <discovery>2018-09-29</discovery>
+      <entry>2018-10-11</entry>
+    </dates>
+  </vuln>
+
   <vuln vid="cb539d4e-cd68-11e8-8819-00e04c1ea73d">
     <topic>gitea -- multiple vulnerabilities</topic>
     <affects>
