From owner-svn-ports-head@freebsd.org Fri Dec 9 19:44:13 2016 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AD1CC6EE52; Fri, 9 Dec 2016 19:44:13 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1562C1B5D; Fri, 9 Dec 2016 19:44:13 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id uB9JiCAf032193; Fri, 9 Dec 2016 19:44:12 GMT (envelope-from madpilot@FreeBSD.org) Received: (from madpilot@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id uB9JiC2S032191; Fri, 9 Dec 2016 19:44:12 GMT (envelope-from madpilot@FreeBSD.org) Message-Id: <201612091944.uB9JiC2S032191@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: madpilot set sender to madpilot@FreeBSD.org using -f From: Guido Falsi Date: Fri, 9 Dec 2016 19:44:12 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r428237 - head/security/vuxml X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2016 19:44:13 -0000 Author: madpilot Date: Fri Dec 9 19:44:11 2016 New Revision: 428237 URL: https://svnweb.freebsd.org/changeset/ports/428237 Log: Document vulnerabilities in net/asterisk11 and net/asterisk13. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Fri Dec 9 19:30:19 2016 (r428236) +++ head/security/vuxml/vuln.xml Fri Dec 9 19:44:11 2016 (r428237) @@ -58,6 +58,92 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + asterisk -- Authentication Bypass + + + asterisk11 + 11.25.1 + + + asterisk13 + 13.13.1 + + + + +

The Asterisk project reports:

+
The chan_sip channel driver has a liberal definition + for whitespace when attempting to strip the content between + a SIP header name and a colon character. Rather than + following RFC 3261 and stripping only spaces and horizontal + tabs, Asterisk treats any non-printable ASCII character + as if it were whitespace.
+
This mostly does not pose a problem until Asterisk is + placed in tandem with an authenticating SIP proxy. In + such a case, a crafty combination of valid and invalid + To headers can cause a proxy to allow an INVITE request + into Asterisk without authentication since it believes + the request is an in-dialog request. However, because of + the bug described above, the request will look like an + out-of-dialog request to Asterisk. Asterisk will then + process the request as a new call. The result is that + Asterisk can process calls from unvetted sources without + any authentication.
+
If you do not use a proxy for authentication, then + this issue does not affect you.
+
If your proxy is dialog-aware (meaning that the proxy + keeps track of what dialogs are currently valid), then + this issue does not affect you.
+
If you use chan_pjsip instead of chan_sip, then this + issue does not affect you.
+

+ + + + http://downloads.digium.com/pub/security/ASTERISK-2016-009.html + + + 2016-11-28 + 2016-12-09 + + + + + asterisk -- Crash on SDP offer or answer from endpoint using Opus + + + asterisk13 + 13.12.013.13.1 + + + + +

The Asterisk project reports:

+
If an SDP offer or answer is received with the Opus + codec and with the format parameters separated using a + space the code responsible for parsing will recursively + call itself until it crashes. This occurs as the code + does not properly handle spaces separating the parameters. + This does NOT require the endpoint to have Opus configured + in Asterisk. This also does not require the endpoint to + be authenticated. If guest is enabled for chan_sip or + anonymous in chan_pjsip an SDP offer or answer is still + processed and the crash occurs.
+

+ + + + http://downloads.asterisk.org/pub/security/AST-2016-008.html + + + 2016-11-11 + 2016-12-09 + + + cryptopp -- multiple vulnerabilities