CVE-2020-0838

NTFS Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: September 11, 2020 at 05:08 PM UTC
Updated: June 17, 2026 at 02:46 AM UTC
19 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 2004 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 2004 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 1.0%
SSVC
No known exploit

Description

<p>An elevation of privilege vulnerability exists when NTFS improperly checks access. An attacker who successfully exploited this vulnerability could run processes in an elevated context.</p> <p>To exploit the vulnerability, an attacker would first have to log on to the system, and then run a specially crafted application to take control over the affected system.</p> <p>The security update addresses the vulnerability by correcting how NTFS checks access.</p>

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.3.0 ≤ v < publication6.3.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.0.0 ≤ v < publication6.1.0 ≤ v < publication6.0.06.1.0sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.2.0 ≤ v < publication6.3.0 ≤ v < publication6.2.06.3.0r2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0190319092004
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card