diff options
| -rw-r--r-- | security/vuxml/vuln.xml | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml index 3ad2436d4887..a171d381500d 100644 --- a/security/vuxml/vuln.xml +++ b/security/vuxml/vuln.xml @@ -58,6 +58,81 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> + <vuln vid="818b2bcb-a46f-11e9-bed9-001999f8d30b"> + <topic>asterisk -- Remote crash vulnerability with MESSAGE messages</topic> + <affects> + <package> + <name>asterisk13</name> + <range><lt>13.27.1</lt></range> + </package> + <package> + <name>asterisk15</name> + <range><lt>15.7.3</lt></range> + </package> + <package> + <name>asterisk16</name> + <range><lt>16.4.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 specially crafted SIP in-dialog MESSAGE message can cause Asterisk to crash.</p> + </blockquote> + </body> + </description> + <references> + <url>https://downloads.asterisk.org/pub/security/AST-2019-002.html</url> + <cvename>CVE-2019-12827</cvename> + </references> + <dates> + <discovery>2019-06-13</discovery> + <entry>2019-07-12</entry> + </dates> + </vuln> + + <vuln vid="e9d2e981-a46d-11e9-bed9-001999f8d30b"> + <topic>asterisk -- Remote Crash Vulnerability in chan_sip channel driver</topic> + <affects> + <package> + <name>asterisk13</name> + <range><lt>13.27.1</lt></range> + </package> + <package> + <name>asterisk15</name> + <range><lt>15.7.3</lt></range> + </package> + <package> + <name>asterisk16</name> + <range><lt>16.4.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>When T.38 faxing is done in Asterisk a T.38 reinvite + may be sent to an endpoint to switch it to T.38. If the + endpoint responds with an improperly formatted SDP answer + including both a T.38 UDPTL stream and an audio or video + stream containing only codecs not allowed on the SIP peer + or user a crash will occur. The code incorrectly assumes + that there will be at least one common codec when T.38 + is also in the SDP answer.</p> + </blockquote> + </body> + </description> + <references> + <url>https://downloads.asterisk.org/pub/security/AST-2019-003.html</url> + <cvename>CVE-2019-13161</cvename> + </references> + <dates> + <discovery>2019-06-28</discovery> + <entry>2019-07-12</entry> + </dates> + </vuln> + <vuln vid="a449c604-a43a-11e9-b422-fcaa147e860e"> <topic>python 3.7 -- multiple vulnerabilities</topic> <affects> |