nday
CVE-2020-16911

GDI+ Remote Code Execution Vulnerability

Microsoft / Windows 10 Version 1803, Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows 10 Version 1909, Windows Server, version 1909 (Server Core installation) +17

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
Windows
affected products in the CVE record: Microsoft · Windows 10 Version 1507, Microsoft · Windows 10 Version 1607, Microsoft · Windows 10 Version 1709, Microsoft · Windows 10 Version 1709 for 32-bit Systems, Microsoft · Windows 10 Version 1803, Microsoft · Windows 10 Version 1809, Microsoft · Windows 10 Version 1903 for 32-bit Systems, Microsoft · Windows 10 Version 1903 for ARM64-based Systems, Microsoft · Windows 10 Version 1903 for x64-based Systems, Microsoft · Windows 10 Version 1909 and 2 moreCPE names NVD's analysts give as vulnerable: o:microsoft:windows_10, o:microsoft:windows_7, o:microsoft:windows_8.1, o:microsoft:windows_rt_8.1
Windows Server
affected products in the CVE record: Microsoft · Windows Server 2012, Microsoft · Windows Server 2012 (Server Core installation), Microsoft · Windows Server 2012 R2, Microsoft · Windows Server 2012 R2 (Server Core installation), Microsoft · Windows Server 2016, Microsoft · Windows Server 2016 (Server Core installation), Microsoft · Windows Server 2019, Microsoft · Windows Server 2019 (Server Core installation), Microsoft · Windows Server version 2004, Microsoft · Windows Server, version 1903 (Server Core installation) and 1 moreCPE names NVD's analysts give as vulnerable: o:microsoft:windows_server_2012, o:microsoft:windows_server_2016, o:microsoft:windows_server_2019
operating system
affected products in the CVE record: Microsoft · Windows 10 Version 1507, Microsoft · Windows 10 Version 1607, Microsoft · Windows 10 Version 1709, Microsoft · Windows 10 Version 1709 for 32-bit Systems, Microsoft · Windows 10 Version 1803, Microsoft · Windows 10 Version 1809, Microsoft · Windows 10 Version 1903 for 32-bit Systems, Microsoft · Windows 10 Version 1903 for ARM64-based Systems, Microsoft · Windows 10 Version 1903 for x64-based Systems, Microsoft · Windows 10 Version 1909 and 13 moreCPE names NVD's analysts give as vulnerable: o:microsoft:windows_10, o:microsoft:windows_7, o:microsoft:windows_8.1, o:microsoft:windows_rt_8.1, o:microsoft:windows_server_2012, o:microsoft:windows_server_2016, o:microsoft:windows_server_2019the product type of Windows and Windows Server in nday's product registry
stage
DIS
disclosed
cvss
8.8 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2020-10-16T22:17Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

<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>

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

CVSS 3.1 vector from the CVE record, scored by the CNA microsoft.

Event log

+DISdisclosed

CVE record published by microsoft. CVSS 8.8, high.

src cvelist · nday , bulk import · raw
{
  "id": 224554,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2020-16911",
  "occurred_at": "2020-10-16T22:17:45Z",
  "observed_at": "2026-11-13T05:37:10.972872Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2020-10-16T22:17:45.000Z",
    "assigner_short_name": "microsoft"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.