Low
CVE-2020-0605
Add Reference
Description
URL
Type
CVE-2020-0605
MITRE ATT&CK
Collection
Command and Control
Credential Access
Defense Evasion
Discovery
Execution
Exfiltration
Impact
Initial Access
Lateral Movement
Persistence
Privilege Escalation
Description
A remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file.An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user, aka ‘.NET Framework Remote Code Execution Vulnerability’. This CVE ID is unique from CVE-2020-0606.
Add Assessment
Ratings
-
Attacker ValueLow
-
ExploitabilityMedium
Technical Analysis
A vulnerability exists in how Microsoft’s XPS documents are processed using .NET that can be leveraged to execute code using a deserialization attack. XPS files are effectively ZIP archives containing multiple member, of which ones .fdoc
, and .fpage
can be used as triggers. While this vulnerability was patched in May of 2020, it’s related to a similar vulnerability patched in January of 2020, which patched the same usage of the XPS document’s .fdseq
member file types.
The default XPS viewer in Windows does not use .NET to render the XPS document making it unaffected by this vulnerability. A vulnerable application would need to be configured to process a maliciously crafted XPS document. Due to this, it is unclear if in practice this vulnerability will require user interaction or authentication to leverage.
See: https://www.mdsec.co.uk/2020/05/analysis-of-cve-2020-0605-code-execution-using-xps-files-in-net/
CVSS V3 Severity and Metrics
General Information
Vendors
- Microsoft
Products
- .NET Core,
- Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2,
- Microsoft .NET Framework 3.0,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1909 (Server Core installation),
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1909 for x64-based Systems,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server, version 1803 (Server Core Installation),
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for 32-bit Systems,
- Microsoft .NET Framework 4.8 on Windows Server, version 1803 (Server Core Installation),
- Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit Systems,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit Systems,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based Systems,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based Systems,
- Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation),
- Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation),
- Microsoft .NET Framework 4.8 on Windows Server 2012,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems,
- Microsoft .NET Framework 4.8 on Windows Server 2012 R2,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019,
- Microsoft .NET Framework 4.6,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems,
- Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019,
- Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1,
- Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation),
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation),
- Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation),
- Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation),
- Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systems,
- Microsoft .NET Framework 4.8 on Windows Server 2016,
- Microsoft .NET Framework 4.8 on Windows RT 8.1,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems,
- Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation),
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems,
- Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based Systems,
- Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1,
- Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systems,
- Microsoft .NET Framework 4.5.2,
- Microsoft .NET Framework 3.5.1,
- Microsoft .NET Framework 3.5,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1803 for x64-based Systems,
- Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 for x64-based Systems,
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for 32-bit Systems,
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016,
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 (Server Core installation),
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for x64-based Systems,
- Microsoft .NET Framework 3.5 AND 4.7.1/4.7.2 on Windows 10 Version 1709 for x64-based Systems
References
Additional Info
Technical Analysis
Report as Exploited in the Wild
What do we mean by "exploited in the wild"?
By selecting this, you are verifying to the AttackerKB community that either you, or a reputable source (example: a security vendor or researcher), has observed an active attempt by attackers, or IOCs related, to exploit this vulnerability outside of a research environment.
A vulnerability should also be considered "exploited in the wild" if there is a publicly available PoC or exploit (example: in an exploitation framework like Metasploit).