Microsoft Graphics Remote Code Execution Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 2 on Exploit-DB
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A remote code execution vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. An attacker who successfully exploited the 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. There are multiple ways an attacker could exploit the vulnerability: 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 click a link in an email or instant message that takes users to the attacker's website, or by opening an attachment sent through email. In a file-sharing attack scenario, an attacker could provide a specially crafted document file designed to exploit the vulnerability and then convince users to open the document file. The security update addresses the vulnerability by correcting how the Windows font library handles embedded fonts.
Timeline
- CVE published
- Public exploit on Exploit-DB
EDB-47265, EDB-47267
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Microsoft Windows 10 Version 1703
From 10.0.0
- Microsoft Windows 10 Version 1803
From 10.0.0
- Microsoft Windows Server, version 1803 (Server Core Installation)
From 10.0.0
- Microsoft Windows 10 Version 1809
From 10.0.0
- Microsoft Windows Server 2019
From 10.0.0
- Microsoft Windows Server 2019 (Server Core installation)
From 10.0.0
- Microsoft Windows 10 Version 1709 for 32-bit Systems
From 10.0.0
- Microsoft Windows 10 Version 1709
From 10.0.0
- Microsoft Windows 10 Version 1903 for 32-bit Systems
From 10.0.0
- Microsoft Windows 10 Version 1903 for x64-based Systems
From 10.0.0
- Microsoft Windows 10 Version 1903 for ARM64-based Systems
From 10.0.0
- Microsoft Windows Server, version 1903 (Server Core installation)
From 10.0.0
- Microsoft Windows 10 Version 1507
From 10.0.0
- Microsoft Windows 10 Version 1607
From 10.0.0
- Microsoft Windows Server 2016
From 10.0.0
- Microsoft Windows Server 2016 (Server Core installation)
From 10.0.0
- Microsoft Windows 7
From 6.1.0
- Microsoft Windows 7 Service Pack 1
From 6.1.0
- Microsoft Windows 8.1
From 6.3.0
- Microsoft Windows Server 2008 Service Pack 2
From 6.0.0
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
From 6.0.0
- Microsoft Windows Server 2008 Service Pack 2
From 6.0.0
- Microsoft Windows Server 2008 R2 Systems Service Pack 1
From 6.1.0
- Microsoft Windows Server 2008 R2 Service Pack 1
From 6.1.0
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
From 6.0.0
- Microsoft Windows Server 2012
From 6.2.0
- Microsoft Windows Server 2012 (Server Core installation)
From 6.2.0
- Microsoft Windows Server 2012 R2
From 6.3.0
- Microsoft Windows Server 2012 R2 (Server Core installation)
From 6.3.0