CVE-2020-1412: Critical severity windows 10 vulnerability
Published Jul 14, 2020
·Updated
A remote code execution vulnerability exists in the way that Microsoft Graphics Components handle objects in memory, aka 'Microsoft Graphics Components Remote Code Execution Vulnerability'.
Affected Software
36 affected components
Microsoft Windows 10
Microsoft Windows 10
Microsoft Windows 10=1607
Microsoft Windows 10=1607
Microsoft Windows 10=1709
Microsoft Windows 10=1709
Microsoft Windows 10=1709
Microsoft Windows 10=1803
Microsoft Windows 10=1803
Microsoft Windows 10=1803
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1903
Microsoft Windows 10=1903
Microsoft Windows 10=1903
Microsoft Windows 10=1909
Microsoft Windows 10=1909
Microsoft Windows 10=1909
Microsoft Windows 10=2004
Microsoft Windows 10=2004
Microsoft Windows 10=2004
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
Microsoft Windows Server 2016=1903
Microsoft Windows Server 2016=1909
Microsoft Windows Server 2016=2004
Microsoft Windows Server 2019
Remediation
Event History
Jul 14, 2020
CVE Published
via MITRE·10:54 PM
Data Sourced
via MITRE·10:54 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2020-1412?
CVE-2020-1412 has a severity rating of Critical.
2
How do I fix CVE-2020-1412?
To fix CVE-2020-1412, ensure that you apply the latest Microsoft updates for your affected version of Windows.
3
What can attackers do with CVE-2020-1412?
Attackers can exploit CVE-2020-1412 to execute arbitrary code on affected systems.
4
Which versions of Windows are affected by CVE-2020-1412?
CVE-2020-1412 affects multiple versions of Windows, including Windows 7, Windows 8.1, Windows 10, and several Windows Server editions.
5
Is there any workaround for CVE-2020-1412?
No official workarounds for CVE-2020-1412 are provided; applying the appropriate security updates is recommended.