Skip to content
Server Security Center
KEVhigh7.8

CVE-2020-1464: Microsoft Windows Spoofing

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
39%
higher than 98.6% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2020-1464 explained

CVE-2020-1464 is a spoofing vulnerability in Microsoft Windows caused by incorrect validation of file signatures. An attacker who exploits it can bypass security features and load improperly signed files. CISA lists it as known to be exploited, so unpatched systems face real risk.

Impact

An attacker can bypass security features meant to block improperly signed files and get such files loaded. The CVSS vector shows local access with low privileges, no user interaction and high impact on confidentiality, integrity and availability. CISA's SSVC rates technical impact as total and automatable as no. CISA lists the vulnerability as known exploited. Known ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1709, 1803, 1809, 1903 and 1909, Windows Server 2019 (including Server Core), and Windows Server, version 1903 and 1909 (Server Core installation). In each case, builds before the security update of 2020-08-11 are affected. The fix is the security update of 2020-08-11. The page lists 17 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

A spoofing vulnerability exists when Windows incorrectly validates file signatures. An attacker who successfully exploited this vulnerability could bypass security features and load improperly signed files. In an attack scenario, an attacker could bypass security features intended to prevent improperly signed files from being loaded.

The update addresses the vulnerability by correcting how Windows validates file signatures.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180332-bit, x64, ARM64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2019x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server, version 1909 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 1709 for 32-bit Systems32-bit
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 1709x64, ARM64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 1903 for x64-based Systems
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
Show 19 more products
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server, version 1903 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server version 2004x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2016x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 732-bit
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2012x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2012 R2x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-08-11
    Fixed in
    • security update of 2020-08-11

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1803: security update of 2020-08-11
    • Microsoft Windows 10 Version 1809: security update of 2020-08-11
    • Microsoft Windows Server 2019: security update of 2020-08-11
    • Microsoft Windows Server 2019 (Server Core installation): security update of 2020-08-11
    • Microsoft Windows 10 Version 1909: security update of 2020-08-11
    • Microsoft Windows Server, version 1909 (Server Core installation): security update of 2020-08-11
    Fixed versions for 23 more products are in the table above.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update of 2020-08-11 or a later cumulative update on all affected Windows 10 and Windows Server systems.
  2. Follow the Microsoft vendor advisory for the exact update for each version and platform.
  3. Use your patch management tooling to confirm that no affected system is missing the update.
  4. Limit local access and low-privileged accounts on critical systems to reduce exposure.
  5. Check unpatched or previously unpatched systems for signs of compromise, such as unexpected improperly signed files.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-347 Improper Verification of Cryptographic Signature

Questions about CVE-2020-1464

Is CVE-2020-1464 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03. Whether it has been used in ransomware campaigns is listed as unknown.
Which update fixes it?
The CVE record names the security update of 2020-08-11 as the fix for all listed Windows 10 and Windows Server versions. The update corrects how Windows validates file signatures.
What does CISA require?
CISA's required action is to apply updates per vendor instructions. The due date for US federal agencies was 2022-05-03.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.