CVE-2020-16911 A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects…
Description
<p>A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory. An attacker who successfully exploited this vulnerability could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.</p> <p>There are multiple ways an attacker could exploit the vulnerability:</p> <ul> <li>In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability and then convince users to view the website. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to open an email attachment or click a link in an email or instant message.</li> <li>In a file-sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit the vulnerability, and then convince users to open the document file.</li> </ul> <p>The security update addresses the vulnerability by correcting the way that the Windows GDI handles objects in the memory.</p>
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Windows 10 Version 1803 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1809 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server 2019 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server 2019 (Server Core installation) 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1909 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server, version 1909 (Server Core installation) 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1709 for 32-bit Systems 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1709 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1903 for 32-bit Systems 10.0 | 10.0.0 → latest | No fix stated |
Show the 14 other branches Hide the 14 other branches
| Product | Affected versions | Fixed in |
|---|---|---|
| Windows 10 Version 1903 for x64-based Systems 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1903 for ARM64-based Systems 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server, version 1903 (Server Core installation) 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 2004 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server version 2004 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1507 10.0 | 10.0.0 → latest | No fix stated |
| Windows 10 Version 1607 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server 2016 10.0 | 10.0.0 → latest | No fix stated |
| Windows Server 2016 (Server Core installation) 10.0 | 10.0.0 → latest | No fix stated |
| Windows 8.1 6.3 | 6.3.0 → latest | No fix stated |
| Windows Server 2012 6.2 | 6.2.0 → latest | No fix stated |
| Windows Server 2012 (Server Core installation) 6.2 | 6.2.0 → latest | No fix stated |
| Windows Server 2012 R2 6.3 | 6.3.0 → latest | No fix stated |
| Windows Server 2012 R2 (Server Core installation) 6.3 | 6.3.0 → latest | No fix stated |
References
- portal.msrc.microsoft.com portal.msrc.microsoft.com
Timeline
- Published
- Last modified