Date: Thu, 2 Aug 2012 12:59:58 +0000 (UTC) From: Ryan Steinmetz <zi@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r301862 - head/security/vuxml Message-ID: <201208021259.q72CxwXJ083854@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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 <body xmlns="http://www.w3.org/1999/xhtml">; <p>ISC reports:</p> <blockquote cite="https://www.isc.org/announcement/bind-and-dhcp-security-updates-released">; - <p>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.</p> - <p>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.</p> + <p>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.</p> + <p>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.</p> <p>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.)</p> + 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.)</p> </blockquote> </body> </description>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208021259.q72CxwXJ083854>