aboutsummaryrefslogtreecommitdiff
path: root/security/vuxml
diff options
context:
space:
mode:
authorCraig Leres <leres@FreeBSD.org>2019-08-09 16:47:32 +0000
committerCraig Leres <leres@FreeBSD.org>2019-08-09 16:47:32 +0000
commit0a8a02fb5f1c68a007f36c26f703a8ba807cc8dd (patch)
treed2ee424fbfa08c3700222210f8cbce4c4d17c160 /security/vuxml
parente4d93c1e8d471881537f868764fa9dc487e59391 (diff)
downloadports-0a8a02fb5f1c68a007f36c26f703a8ba807cc8dd.tar.gz
ports-0a8a02fb5f1c68a007f36c26f703a8ba807cc8dd.zip
Notes
Diffstat (limited to 'security/vuxml')
-rw-r--r--security/vuxml/vuln.xml44
1 files changed, 44 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index f51c654dc0e2..99ed2adbc54e 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -58,6 +58,50 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="f56669f5-d799-4ff5-9174-64a6d571c451">
+ <topic>bro -- Null pointer dereference and Signed integer overflow</topic>
+ <affects>
+ <package>
+ <name>bro</name>
+ <range><lt>2.6.3</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>Jon Siwek of Corelight reports:</p>
+ <blockquote cite="https://raw.githubusercontent.com/zeek/zeek/1d874e5548a58b3b8fd2a342fe4aa0944e779809/NEWS">
+ <p>This is a security patch release to address potential
+ Denial of Service vulnerabilities:</p>
+ <ul>
+ <li>
+ Null pointer dereference in the RPC analysis code. RPC
+ analyzers (e.g. MOUNT or NFS) are not enabled in the
+ default configuration.</li>
+
+ <li>
+ Signed integer overflow in BinPAC-generated parser code.
+ The result of this is Undefined Behavior with respect to
+ the array bounds checking conditions that BinPAC generates,
+ so it's unpredictable what an optimizing compiler may
+ actually do under the assumption that signed integer
+ overlows should never happen. The specific symptom which
+ lead to finding this issue was with the PE analyzer causing
+ out-of-memory crashes due to large allocations that were
+ otherwise prevented when the array bounds checking logic
+ was changed to prevent any possible signed integer overlow.</li>
+ </ul>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <url>https://raw.githubusercontent.com/zeek/zeek/1d874e5548a58b3b8fd2a342fe4aa0944e779809/NEWS</url>
+ </references>
+ <dates>
+ <discovery>2019-06-22</discovery>
+ <entry>2019-08-09</entry>
+ </dates>
+ </vuln>
+
<vuln vid="9de4c1c1-b9ee-11e9-82aa-6cc21735f730">
<topic>PostgresSQL -- TYPE in pg_temp execute arbitrary SQL during `SECURITY DEFINER` execution</topic>
<affects>