Skip to content
Fencer Intel
high 8.8

CVE-2020-1412 in the critical feed json

A remote code execution vulnerability exists in the way that Microsoft Graphics Components handle objects in memory, aka 'Microsoft Graphic…

published 6y ago modified 4mo ago also EUVD-2020-12288

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.0%
EPSS 14.0% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

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

Patch / fix

Is CVE-2020-1412 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

13.98% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows 10 Version 2004 for 32-bit Systems
  • Microsoft Windows 10 Version 2004 for x64-based Systems
  • Microsoft Windows 10 Version 2004 for ARM64-based Systems
  • Microsoft Windows Server, version 2004 (Server Core installation)
  • Microsoft Windows
  • Microsoft Windows Server
  • Microsoft Windows 10 Version 1909 for 32-bit Systems
  • Microsoft Windows 10 Version 1909 for x64-based Systems
  • Microsoft Windows 10 Version 1909 for ARM64-based Systems
  • Microsoft Windows Server, version 1909 (Server Core installation)
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Windows 10 Version 1903 for x64-based Systems
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Windows Server, version 1903 (Server Core installation)

Classification

Weakness
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.