CVE-2017-8686

Windows DHCP Server Remote Code Execution Vulnerability

CVE-2017-8686 is fixed in 6 products on 1 platform, first by KB4038782, released September 12, 2017. It is not reported as exploited. Patch Radar priority: Urgent.

Urgent
CVSS
9.8
Critical
Exploitation
None reported
Exploitation Less Likely
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.2750
98th percentile

<p>A memory corruption vulnerability exists in the Windows Server DHCP service when an attacker sends specially crafted packets to a DHCP failover server. An attacker who successfully exploited the vulnerability could either run arbitrary code on the DHCP failover server or cause the DHCP service to become nonresponsive.</p> <p>To exploit the vulnerability, an attacker could send a specially crafted packet to a DHCP server. However, the DHCP server must be set to failover mode for the attack to succeed.</p> <p>The security update addresses the vulnerability by correcting how DHCP failover servers handle network packets.</p>

Where it's fixed

ProductFixed inFixReleased
Microsoft
Windows Server 2012 KB4038786 Sep 12, 2017
Windows Server 2012 KB4038799 Sep 12, 2017
Windows Server 2012 (Server Core installation) KB4038786 Sep 12, 2017
Windows Server 2012 (Server Core installation) KB4038799 Sep 12, 2017
Windows Server 2012 R2 KB4038792 Sep 12, 2017
Windows Server 2012 R2 KB4038793 Sep 12, 2017
Windows Server 2012 R2 (Server Core installation) KB4038792 Sep 12, 2017
Windows Server 2012 R2 (Server Core installation) KB4038793 Sep 12, 2017
Windows Server 2016 14393.1715 KB4038782 Sep 12, 2017
Windows Server 2016 (Server Core installation) 14393.1715 KB4038782 Sep 12, 2017

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.