CVE-2015-8605: UDP payload length not properly checked
  • 16 Nov 2018
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF

CVE-2015-8605: UDP payload length not properly checked

  • Dark
  • PDF

Article Summary

CVE: CVE-2015-8605

Document version: 2.0

Posting date: 12 January 2016

Program impacted: ISC DHCP

Versions affected: 4.0.x, 4.1.x, 4.2.x, 4.1-ESV -> 4.1-ESV-R12, 4.3.0->4.3.3. 3.x may also be affected but has not been tested.

Severity: Medium

Exploitable: From adjacent networks


A badly formed packet with an invalid IPv4 UDP length field can cause a DHCP server, client, or relay program to terminate abnormally.


Nearly all IPv4 DHCP clients and relays, and most IPv4 DHCP servers, are potentially affected.

A server, client, or relay that is built to only be able to process unicast packets (i.e. those that have already been processed by the OS UDP/IP stack) is not affected; however, this build configuration is not normally viable for clients and relays. Servers with this build configuration require a relay in order to be able to process DISCOVER and other broadcast requests from clients.

Not all potentially affected builds will actually be affected, but because it is difficult to identify or predict those which should be upgraded, our advice is that all builds should be considered vulnerable.

CVSS Score: 5.7

CVSS Vector: (AV:A/AC:M/Au:N/C:N/I:N/A:C)

For more information on the Common Vulnerability Scoring System and to obtain your specific environmental score please visit:


None likely, but in some environments following the advice from Securing Your Network From DHCP Risks can substantially reduce the risk by limiting the exposure of an ISC DHCP server to "controlled" networks and clients.

Active exploits: No known active exploits.

Solution: Upgrade to the patched release most closely related to your current version of ISC DHCP. These can all be downloaded from

  • DHCP version 4.1-ESV-R12-P1
  • DHCP version 4.3.3-P1

Acknowledgements: Thanks to Sebastian Poehn from Sophos for reporting this issue.

Document Revision History:

1.0 Advance Notification, 5 January 2016
1.1 ESV Version name corrected, 12 January 2016
2.0 Public Disclosure, 12 January 2016

Related documents:

Do you still have questions? Questions regarding this advisory should go to [email protected]. To report a new issue, please encrypt your message using [email protected]'s PGP key which can be found here: If you are unable to use encrypted email, you may also report new issues at:


ISC patches only currently supported versions. When possible we indicate EOL versions affected. (For current information on which versions are actively supported, please see

ISC Security Vulnerability Disclosure Policy:

Details of our current security advisory policy and practice can be found in the ISC Software Defect and Security Vulnerability Disclosure Policy.

This Knowledgebase article is the complete and official security advisory document.

Legal Disclaimer:

Internet Systems Consortium (ISC) is providing this notice on an "AS IS" basis. No warranty or guarantee of any kind is expressed in this notice and none should be implied. ISC expressly excludes and disclaims any warranties regarding this notice or materials referred to in this notice, including, without limitation, any implied warranty of merchantability, fitness for a particular purpose, absence of hidden defects, or of non-infringement. Your use or reliance on this notice or materials referred to in this notice is at your own risk. ISC may change this notice at any time. A stand-alone copy or paraphrase of the text of this document that omits the document URL is an uncontrolled copy. Uncontrolled copies may lack important information, be out of date, or contain factual errors.