Vulnerability Note VU#159528

ISC DHCP server vulnerability

Original Release date: 13 Dec 2010 | Last revised: 13 Dec 2010

Overview

The ISC DHCP server contains a vulnerability that could allow a remote attacker to cause a denial of service.

Description

According to ISC:

If a TCP connection is established to the server on a port which has been configured for communication with a failover peer, this can cause it to become non-responsive to all normal DHCP protocol traffic. The server will progress to a communications-interrupted state - but in addition will also cease to provide DHCP services to clients. The server must be restarted to resume normal operation.
This can be used as an attack vector against servers that are configured for failover partnerships.

Impact

An unauthenticated remote attacker could cause the server to become unresponsive to all normal DHCP protocol traffic, thereby creating a denial of service.

Solution

Apply an update

Users who obtain ISC DHCP from a third-party vendor, such as their operating system vendor, should see the vendor information portion of this document for a partial list of affected vendors.

This vulnerability is addressed in ISC DHCP version 4.2.0-P2. Users of ISC DHCP from the original source distribution should upgrade to this version or later, as appropriate.

See also https://www.isc.org/software/dhcp/advisories/cve-2010-3616

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
Internet Systems Consortium - DHCPAffected-13 Dec 2010
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Thanks to Internet Systems Consortium for reporting this vulnerability.

This document was written by Michael Orlando.

Other Information

  • CVE IDs: CVE-2010-3616
  • Date Public: 13 Dec 2010
  • Date First Published: 13 Dec 2010
  • Date Last Updated: 13 Dec 2010
  • Severity Metric: 11.81
  • Document Revision: 9

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.