BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-16922High confidence

Windows Spoofing Vulnerability

Microsoft · Windows 10 Version 1803

5.3MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.81% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Microsoft Windows 10 Version 1803 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2020-8880

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

<p>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.</p> <p>In an attack scenario, an attacker could bypass security features intended to prevent improperly signed files from being loaded.</p> <p>The update addresses the vulnerability by correcting how Windows validates file signatures.</p>

What

<p>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.</p> <p>In an attack scenario, an attacker could bypass security features intended to prevent improperly signed files from being loaded.</p> <p>The update addresses the vulnerability by correcting how Windows validates file signatures.</p>

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

<p>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.</p> <p>In an attack scenario, an attacker could bypass security features intended to prevent improperly signed files from being loaded.</p> <p>The update addresses the vulnerability by correcting how Windows validates file signatures.</p>

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Verification of Cryptographic Signature → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-347 ↗

CWE-347: Improper Verification of Cryptographic Signature. The product does not verify, or incorrectly verifies, the cryptographic signature for data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-347
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20201021Security Bulletin 21 Oct 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Oct 2020, published on 21 October 2020. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-634Multiples vulnérabilités dans Microsoft Windows

d?id=CVE-2020-16911 Référence CVE CVE-2020-16912 https://www.cve.org/CVERecord?id=CVE-2020-16912 Référence CVE CVE-2020-16913 https://www.cve.org/CVERecord?id=CVE-2020-16913 Référence CVE CVE-2020-16914 https://www.cve.org/CVERecord?id=CVE-2020-16914 Référence CVE CVE-2020-16915 https://www.cve.org/CVERecord?id=CVE-2020-16915 Référence CVE CVE-2020-16916 https://www.cve.org/CVERecord?id=CVE-2020-16916 Référence CVE CVE-2020-16919 https://www.cve.org/CVERecord?id=CVE-2020-16919 Référence CVE CVE-2020-16920 https://www.cve.org/CVERecord?id=CVE-2020-16920 Référence CVE CVE-2020-16921 https://www.cve.org/CVERecord?id=CVE-2020-16921 Référence CVE CVE-2020-16922 https://www.cve.org/CVERecord?id=CVE-2020-16922 Référence CVE CVE-2020-16923 https://www.cve.org/CVERecord?id=CVE-2020-16923 Référence CVE CVE-2020-16924 https://www.cve.org/CVERecord?id=CVE-2020-16924 Référence CVE CVE-2020-16927 https://www.cve.org/CVERecord?id=CVE-2020-16927 Référence CVE CVE-2020-16935 https://www.cve.org/CVERecord?id=CVE-2020-16935 Référence CVE CVE-2020-16936 https://www.cve.org/CVERecord?id=CVE-2020-16936 Référence CVE CVE-2020-16938 https://www.cve.org/CVERecord?id=CVE-2020-16938 Référence CVE CVE-2020-16939 https://www.cve.org/CVERecord?id=CVE-2020-16939 Référence CVE CVE-2020-16940 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-009817複数の Microsoft Windows 製品におけるなりすまされる脆弱性

複数の Microsoft Windows 製品には、Windows がファイルの署名を正しく検証しない場合、なりすまされる脆弱性が存在します。 ベンダは、本脆弱性を「Windows のなりすましの脆弱性」として公開しています。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5208MS 10월 보안 위협에 따른 정기 보안 업데이트 권고

- 스푸핑(CVE-2020-16922)

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Oct 2020 · Last source change 4 Aug 2024, 13:45 UTC · CWE-347 · Improper Verification of Cryptographic Signature

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2020-8880
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2020-8880↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-16922 · cve.blacktree.nl