Microsoft Windows DNS
CVE-2018-8626 — Windows DNS Server Heap Overflow Vulnerability
Executive Summary
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. The update addresses the vulnerability by modifying how Windows DNS servers handle requests.
Overview
9.8
CVSS CRITICAL
Critical
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
CVSS Vector
ATTACK VECTOR
Network
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
None
USER INTERACTION
None
SCOPE
Unchanged
CONFIDENTIALITY
High
INTEGRITY
High
AVAILABILITY
High
EXPLOIT CODE MATURITY
Proof-of-Concept
REMEDIATION LEVEL
Official Fix
REPORT CONFIDENCE
Confirmed
Temporal Score: 8.8
EPSS Score
No EPSS score available for this CVE.
View on FIRST.orgAffected Products
17 affected products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Windows 10 Version 1607 for 32-bit Systems | 4471321 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1607 for x64-based Systems | 4471321 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1709 for 32-bit Systems | 4471329 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1709 for ARM64-based Systems | 4471329 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1709 for x64-based Systems | 4471329 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1803 for 32-bit Systems | 4471324 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1803 for ARM64-based Systems | 4471324 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1803 for x64-based Systems | 4471324 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 4471332 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for ARM64-based Systems | 4471332 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows 10 Version 1809 for x64-based Systems | 4471332 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2012 R2 4471320 (Monthly Rollup) 4471322 (Security Only) Critical Remote Code Execution 4467697 Base: 9.8 Temporal: 8.8 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C Yes None Windows Server 2012 R2 (Server Core installation) 4471320 (Monthly Rollup) 4471322 (Security Only) Critical Remote Code Execution 4467697 Base: 9.8 Temporal: 8.8 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C Yes None Windows Server 2016 | 4471321 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2016 (Server Core installation) | 4471321 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2019 | 4471332 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server 2019 (Server Core installation) | 4471332 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server, version 1709 (Server Core Installation) | 4471329 (Security Update) |
Critical | Remote Code Execution | Yes |
| Windows Server, version 1803 (Server Core Installation) | 4471324 (Security Update) |
Critical | Remote Code Execution | Yes |
Patches
4 patches
| Article | Type | Restart |
|---|---|---|
4471321 |
Security Update | Yes |
4471329 |
Security Update | Yes |
4471324 |
Security Update | Yes |
4471332 |
Security Update | Yes |
Known Exploits
No known exploits have been linked for this CVE yet. When available, exploit references will be sourced from public repositories and may be unverified, incomplete, or non-functional. Always review code carefully before use in any environment.
Acknowledgments
Mitch Adair, Microsoft Windows Enterprise Security Team
References
On This Page