CVE Tools

CVE-2020-1464

Windows Spoofing Vulnerability

Exploited in the wild. In CISA KEV since 2021‑11‑03. Fixed in publication.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Windows 10 Version 1803Affected: ≥ 10.0.0, < publicationUpgrade to: publicationStated by: CVE record
  • Microsoft Windows Server 2019Affected: ≥ 10.0.0, < publicationUpgrade to: publicationStated by: CVE record
  • Microsoft Windows Server, version 1909Affected: ≥ 10.0.0, < publicationUpgrade to: publicationStated by: CVE record
  • Microsoft Windows Server 2016Affected: ≥ 10.0.0, < publicationUpgrade to: publicationStated by: CVE record
  • Microsoft Windows 7Affected: ≥ 6.1.0, < publicationUpgrade to: publicationStated by: CVE record

Versions as the sources state them. 5 more products have version data. Full version matrix after sign-in

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2021-11-03.

US federal agencies must remediate by 2022-05-03.

Apply updates per vendor instructions.
Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

39% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 11 days before any public exploit.

  1. OpenVAS check added
  2. EPSS band changelow → moderate
  3. EPSS band changemoderate → low
  4. Public exploit / PoCsource: other
  5. Patch availablerecord updated
  6. Added to CISA KEV

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 Version 1803, not every advisory. This one: actively exploited.