ISC DHCP 4.1 before 4.1.1-P1 and 4.0 before 4.0.2-P1 allows remote attackers to cause a denial of service (server exit) via a zero-length client ID.

A malicious client which is allowed to send very large amounts of traffic (billions of packets) to a DHCP server can eventually overflow a 32-bit reference counter, potentially causing dhcpd to crash.

Versions of DHCP affected: 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0

ISC DHCP 4.1.x before 4.1-ESV-R13 and 4.2.x and 4.3.x before 4.3.4 does not restrict the number of concurrent TCP sessions, which allows remote attackers to cause a denial of service (INSIST assertion failure or request-processing outage) by establishing many sessions.

Failure to properly bounds check a buffer used for processing DHCP options allows a malicious server (or an entity masquerading as a server) to cause a buffer overflow (and resulting crash) in dhclient by sending a response containing a specially constructed options section.

Versions of DHCP affected: 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0

A vulnerability stemming from failure to properly clean up closed OMAPI connections can lead to exhaustion of the pool of socket descriptors available to the DHCP server. Affects ISC DHCP 4.1.0 to 4.1-ESV-R15, 4.2.0 to 4.2.8, 4.3.0 to 4.3.6. Older versions may also be affected but are well beyond their end-of-life (EOL). Releases prior to 4.1.0 have not been tested.

Description from ISC's advisory:

Description:

ISC dhclient has a stack overflow vulnerability which makes it theoretically possible for a rogue DHCP server to execute arbitrary commands as root on the affected system through stack return subversion.

Impact:

While generating a subnet number from the server-supplied leased address and subnet-mask 'dhclient' copies the information into a field without verifying if the length of the information exceeds the length of the field.

Theoretically this allows a rogue DHCP server to execute arbitrary commands as root on the affected system through stack return subversion.

This attack has little to no risk for a client situated on a network that is well defended, whereas clients that are roaming to potentially hostile or ad-hoc networks can see this attack to pose a severe threat.

Factors complicating any attack would be:

1) The attacker would need to generate messages the client views as authentic.

One option is for the attacker to present itself as a suitable DHCPv4 server for a network, in essence operating as a rogue DHCPv4 server.

Another option would be to insert messages into the conversation between the client and the authentic DHCPv4 server. To do this the attacker needs to accurately guess the client's randomly chosen 16-bit transaction ID and insert the attack precisely between the client's request and the valid DHCPv4 server's reply.

Neither of these are likely on a well defended network but clients that are roaming may find them, especially the first, a severe threat.

2) The attacker would then need to develop their attack within a limited packet size.

Support for DHCPv4 total packet size may be limited from 576 octets through the link MTU size (no support for fragmentation) up to 64KB. Of this, the DHCPv4 option payload space is limited by the space taken up by the BOOTP header space, excepting the FILE and SNAME fields (which can be used in 'option overloading' to carry option contents, such as the subnet-mask).

Common Vulnerabilities and Exposures assigned an identifier CVE-2010-3611 to the following vulnerability:

Name: CVE-2010-3611 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3611 Assigned: 20100927 Reference: CONFIRM: http://www.isc.org/software/dhcp/advisories/cve-2010-3611 Reference: CERT-VN:VU#102047 Reference: URL: http://www.kb.cert.org/vuls/id/102047 Reference: BID:44615 Reference: URL: http://www.securityfocus.com/bid/44615 Reference: SECUNIA:42082 Reference: URL: http://secunia.com/advisories/42082 Reference: VUPEN:ADV-2010-2879 Reference: URL: http://www.vupen.com/english/advisories/2010/2879 Reference: XF:iscdhcp-relayforward-dos(62965) Reference: URL: http://xforce.iss.net/xforce/xfdb/62965

ISC DHCP server 4.0 before 4.0.2, 4.1 before 4.1.2, and 4.2 before 4.2.0-P1 allows remote attackers to cause a denial of service (crash) via a DHCPv6 packet containing a Relay-Forward message without an address in the Relay-Forward link-address field.

The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

Multiple memory leaks in ISC DHCP 4.1.x and 4.2.x before 4.2.4-P1 and 4.1-ESV before 4.1-ESV-R6 allow remote attackers to cause a denial of service (memory consumption) by sending many requests.

ISC DHCP 4.1.x before 4.1-ESV-R7 and 4.2.x before 4.2.4-P2 allows remote attackers to cause a denial of service (daemon crash) in opportunistic circumstances by establishing an IPv6 lease in an environment where the lease expiration time is later reduced.

ISC DHCP 4.x before 4.1-ESV-R12-P1, 4.2.x, and 4.3.x before 4.3.3-P1 allows remote attackers to cause a denial of service (application crash) via an invalid length field in a UDP IPv4 packet.