From owner-svn-ports-all@freebsd.org Thu Nov 5 22:38:14 2020 Return-Path: Delivered-To: svn-ports-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C3672D2468; Thu, 5 Nov 2020 22:38:14 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CRz1y28dpz3kh1; Thu, 5 Nov 2020 22:38:14 +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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3D2561ACF3; Thu, 5 Nov 2020 22:38:14 +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 0A5McEeH012866; Thu, 5 Nov 2020 22:38:14 GMT (envelope-from madpilot@FreeBSD.org) Received: (from madpilot@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 0A5McDeY012865; Thu, 5 Nov 2020 22:38:13 GMT (envelope-from madpilot@FreeBSD.org) Message-Id: <202011052238.0A5McDeY012865@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: madpilot set sender to madpilot@FreeBSD.org using -f From: Guido Falsi Date: Thu, 5 Nov 2020 22:38:13 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r554163 - head/security/vuxml X-SVN-Group: ports-head X-SVN-Commit-Author: madpilot X-SVN-Commit-Paths: head/security/vuxml X-SVN-Commit-Revision: 554163 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2020 22:38:14 -0000 Author: madpilot Date: Thu Nov 5 22:38:13 2020 New Revision: 554163 URL: https://svnweb.freebsd.org/changeset/ports/554163 Log: Document asterisk vulnerabilities. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Nov 5 21:59:10 2020 (r554162) +++ head/security/vuxml/vuln.xml Thu Nov 5 22:38:13 2020 (r554163) @@ -58,6 +58,87 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> + + asterisk -- Outbound INVITE loop on challenge with different nonce + + + asterisk13 + 13.37.1 + + + asterisk16 + 16.14.1 + + + asterisk18 + 18.0.1 + + + + +

The Asterisk project reports:

+
If Asterisk is challenged on an outbound INVITE and + the nonce is changed in each response, Asterisk will + continually send INVITEs in a loop. This causes Asterisk + to consume more and more memory since the transaction + will never terminate (even if the call is hung up), + ultimately leading to a restart or shutdown of Asterisk. + Outbound authentication must be configured on the endpoint + for this to occur.
+

+ + + + https://downloads.asterisk.org/pub/security/AST-2020-002.html + + + 2020-11-05 + 2020-11-05 + + + + + asterisk -- Remote crash in res_pjsip_session + + + asterisk13 + 13.37.1 + + + asterisk16 + 16.14.1 + + + asterisk18 + 18.0.1 + + + + +

The Asterisk project reports:

+
Upon receiving a new SIP Invite, Asterisk did not + return the created dialog locked or referenced. This + caused a gap between the creation of the dialog object, + and its next use by the thread that created it. Depending + upon some off nominal circumstances, and timing it was + possible for another thread to free said dialog in this + gap. Asterisk could then crash when the dialog object, + or any of its dependent objects were de-referenced, or + accessed next by the initial creation thread.
+

+ + + + https://downloads.asterisk.org/pub/security/AST-2020-001.html + + + 2020-11-05 + 2020-11-05 + + + chromium -- multiple vulnerabilities