Date: Wed, 6 Jun 2018 16:56:53 +0000 (UTC) From: Craig Leres <leres@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r471860 - head/security/vuxml Message-ID: <201806061656.w56GurQD013473@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: leres Date: Wed Jun 6 16:56:52 2018 New Revision: 471860 URL: https://svnweb.freebsd.org/changeset/ports/471860 Log: Mark bro < 2.5.4 as vulnerable as per: https://www.bro.org/download/NEWS.bro.html Reviewed by: ler (mentor) Approved by: ler (mentor) Differential Revision: https://reviews.freebsd.org/D15677 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Wed Jun 6 16:48:12 2018 (r471859) +++ head/security/vuxml/vuln.xml Wed Jun 6 16:56:52 2018 (r471860) @@ -58,6 +58,33 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">; + <vuln vid="2f4fd3aa-32f8-4116-92f2-68f05398348e"> + <topic>bro -- multiple memory allocation issues</topic> + <affects> + <package> + <name>bro</name> + <range><lt>2.5.4</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>Corelight reports:</p> + <blockquote cite="https://www.bro.org/download/NEWS.bro.html">; + <p>Bro 2.5.4 primarily fixes security issues</p> + <p>Multiple fixes and improvements to BinPAC generated code related to array parsing, with potential impact to all Bro's BinPAC-generated analyzers in the form of buffer over-reads or other invalid memory accesses depending on whether a particular analyzer incorrectly assumed that the evaulated-array-length expression is actually the number of elements that were parsed out from the input.</p> + <p>The NCP analyzer (not enabled by default and also updated to actually work with newer Bro APIs in the release) performed a memory allocation based directly on a field in the input packet and using signed integer storage. This could result in a signed integer overflow and memory allocations of negative or very large size, leading to a crash or memory exhaustion. The new NCP::max_frame_size tuning option now limits the maximum amount of memory that can be allocated.</p> + </blockquote> + </body> + </description> + <references> + <url>https://www.bro.org/download/NEWS.bro.html</url>; + </references> + <dates> + <discovery>2018-05-29</discovery> + <entry>2018-06-06</entry> + </dates> + </vuln> + <vuln vid="c7a135f4-66a4-11e8-9e63-3085a9a47796"> <topic>Git -- Fix memory out-of-bounds and remote code execution vulnerabilities (CVE-2018-11233 and CVE-2018-11235)</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201806061656.w56GurQD013473>