From owner-svn-ports-head@FreeBSD.ORG Thu Aug 2 12:59:59 2012 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3264D106564A; Thu, 2 Aug 2012 12:59:59 +0000 (UTC) (envelope-from zi@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id 129E58FC1A; Thu, 2 Aug 2012 12:59:59 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q72Cxw5f083856; Thu, 2 Aug 2012 12:59:58 GMT (envelope-from zi@svn.freebsd.org) Received: (from zi@localhost) by svn.freebsd.org (8.14.4/8.14.4/Submit) id q72CxwXJ083854; Thu, 2 Aug 2012 12:59:58 GMT (envelope-from zi@svn.freebsd.org) Message-Id: <201208021259.q72CxwXJ083854@svn.freebsd.org> From: Ryan Steinmetz Date: Thu, 2 Aug 2012 12:59:58 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Subject: svn commit: r301862 - head/security/vuxml X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 02 Aug 2012 12:59:59 -0000 Author: zi Date: Thu Aug 2 12:59:58 2012 New Revision: 301862 URL: http://svn.freebsd.org/changeset/ports/301862 Log: - Cleanup whitespace Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu Aug 2 12:48:09 2012 (r301861) +++ head/security/vuxml/vuln.xml Thu Aug 2 12:59:58 2012 (r301862) @@ -301,24 +301,27 @@ Note: Please add new entries to the beg

ISC reports:

-
An unexpected client identifier parameter can cause the ISC DHCP daemon - to segmentation fault when running in DHCPv6 mode, resulting in a denial - of service to further client requests. In order to exploit this - condition, an attacker must be able to send requests to the DHCP server.
-
An error in the handling of malformed client identifiers can cause a DHCP - server running affected versions (see "Impact") to enter a state where - further client requests are not processed and the server process loops - endlessly, consuming all available CPU cycles. - Under normal circumstances this condition should not be triggered, but - a non-conforming or malicious client could deliberately trigger it in a - vulnerable server. In order to exploit this condition an attacker must - be able to send requests to the DHCP server.
+
An unexpected client identifier parameter can cause the ISC DHCP + daemon to segmentation fault when running in DHCPv6 mode, + resulting in a denial of service to further client requests. In + order to exploit this condition, an attacker must be able to send + requests to the DHCP server.
+
An error in the handling of malformed client identifiers can cause + a DHCP server running affected versions (see "Impact") to enter a + state where further client requests are not processed and the + server process loops endlessly, consuming all available CPU + cycles. + Under normal circumstances this condition should not be + triggered, but a non-conforming or malicious client could + deliberately trigger it in a vulnerable server. In order to + exploit this condition an attacker must be able to send requests + to the DHCP server.

Two memory leaks have been found and fixed in ISC DHCP. Both are reproducible when running in DHCPv6 mode (with the -6 command-line - argument.) The first leak is confirmed to only affect servers operating - in DHCPv6 mode, but based on initial code analysis the second may - theoretically affect DHCPv4 servers (though this has not been - demonstrated.)
+ argument.) The first leak is confirmed to only affect servers + operating in DHCPv6 mode, but based on initial code analysis the + second may theoretically affect DHCPv4 servers (though this has + not been demonstrated.)