Date: Thu, 9 Nov 2017 10:12:09 +0000 (UTC) From: Guido Falsi <madpilot@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r453804 - head/security/vuxml Message-ID: <201711091012.vA9AC98w007900@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: madpilot Date: Thu Nov 9 10:12:09 2017 New Revision: 453804 URL: https://svnweb.freebsd.org/changeset/ports/453804 Log: Document Asterisk vulnerabilities. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Nov 9 09:16:25 2017 (r453803) +++ head/security/vuxml/vuln.xml Thu Nov 9 10:12:09 2017 (r453804) @@ -58,6 +58,94 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">; + <vuln vid="be261737-c535-11e7-8da5-001999f8d30b"> + <topic>asterisk -- Memory/File Descriptor/RTP leak in pjsip session resource</topic> + <affects> + <package> + <name>asterisk13</name> + <range><ge>13.5.0</ge><lt>13.18.1</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>The Asterisk project reports:</p> + <blockquote cite="http://www.asterisk.org/downloads/security-advisories">; + <p>A memory leak occurs when an Asterisk pjsip session + object is created and that call gets rejected before the + session itself is fully established. When this happens + the session object never gets destroyed. This then leads + to file descriptors and RTP ports being leaked as well.</p> + </blockquote> + </body> + </description> + <references> + <url>https://downloads.asterisk.org/pub/security/AST-2017-011.html</url>; + </references> + <dates> + <discovery>2017-10-15</discovery> + <entry>2017-11-09</entry> + </dates> + </vuln> + + <vuln vid="ab04cb0b-c533-11e7-8da5-001999f8d30b"> + <topic>asterisk -- Buffer overflow in CDR's set user</topic> + <affects> + <package> + <name>aasterisk13</name> + <range><lt>13.18.1</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>The Asterisk project reports:</p> + <blockquote cite="http://www.asterisk.org/downloads/security-advisories">; + <p>No size checking is done when setting the user field + for Party B on a CDR. Thus, it is possible for someone + to use an arbitrarily large string and write past the end + of the user field storage buffer. The earlier AST-2017-001 + advisory for the CDR user field overflow was for the Party + A buffer.</p> + </blockquote> + </body> + </description> + <references> + <url>https://downloads.asterisk.org/pub/security/AST-2017-010.html</url>; + </references> + <dates> + <discovery>2017-10-09</discovery> + <entry>2017-11-09</entry> + </dates> + </vuln> + + <vuln vid="19b052c9-c533-11e7-8da5-001999f8d30b"> + <topic>asterisk -- Buffer overflow in pjproject header parsing can cause crash in Asterisk</topic> + <affects> + <package> + <name>assterisk13</name> + <range><lt>13.18.1</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml">; + <p>The Asterisk project reports:</p> + <blockquote cite="http://www.asterisk.org/downloads/security-advisories">; + <p>By carefully crafting invalid values in the Cseq and + the Via header port, pjprojects packet parsing code can + create strings larger than the buffer allocated to hold + them. This will usually cause Asterisk to crash immediately. + The packets do not have to be authenticated.</p> + </blockquote> + </body> + </description> + <references> + <url>https://downloads.asterisk.org/pub/security/AST-2017-009.html</url>; + </references> + <dates> + <discovery>2017-10-05</discovery> + <entry>2017-11-09</entry> + </dates> + </vuln> + <vuln vid="f40f07aa-c00f-11e7-ac58-b499baebfeaf"> <topic>OpenSSL -- Multiple vulnerabilities</topic> <affects>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201711091012.vA9AC98w007900>