Windows DNS Server Privilege Escalation vulnerability (CVE-2018-8626) leading to Remote Code execution alleged to have Proof of Concept exploit 14 Dec 2018
AusCERT recently published an ASB addressing Microsoft's security updates for the month of December.
Among the vulnerabilities addressed was a Critical vulnerability in the DNS Server implementation in the following Windows platforms:
"Windows 10 Version 1607 for 32-bit Systems
Windows 10 Version 1607 for x64-based Systems
Windows 10 Version 1709 for 32-bit Systems
Windows 10 Version 1709 for 64-based Systems
Windows 10 Version 1709 for ARM64-based Systems
Windows 10 Version 1803 for 32-bit Systems
Windows 10 Version 1803 for ARM64-based Systems
Windows 10 Version 1803 for x64-based Systems
Windows 10 Version 1809 for 32-bit Systems
Windows 10 Version 1809 for ARM64-based Systems
Windows 10 Version 1809 for x64-based Systems
Windows Server 2012 R2
Windows Server 2012 R2 (Server Core installation)
Windows Server 2016
Windows Server 2016 (Server Core installation)
Windows Server 2019
Windows Server 2019 (Server Core installation)
Windows Server, version 1709 (Server Core Installation)
Windows Server, version 1803 (Server Core Installation)" 
Security updates fixing the vulnerability have been provided by Microsoft.
In their vulnerability description, Microsoft states:
"A remote code execution vulnerability exists in Windows Domain Name System (DNS) servers when they fail to properly handle requests. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the Local System Account. Windows servers that are configured as DNS servers are at risk from this vulnerability.
To exploit the vulnerability, an unauthenticated attacker could send malicious requests to a Windows DNS server." 
Failed exploitation attempts will lead to denial of service conditions.
NVD CVSS3 Vector:
NVD CVSS3 Base Score:
PROOF OF CONCEPT EXPLOIT
Although the NVD CVSS3 vector above indicates a proof of concept exploit exists for this vulnerability, AusCERT has not been able to access it or find any threat indicators related to it. We will continue to update this blog as more information becomes available.
« Back to all blog entries