CVE-2020-0638: An elevation of privilege vulnerability exists in the way the Update Notification Manager handles files.To...
An elevation of privilege vulnerability exists in the way the Update Notification Manager handles files.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Update Notification Manager Elevation of Privilege Vulnerability'.
Security readout for executives and security teams
Plain-English summary
This Windows flaw can let an attacker who already has limited access raise privileges and gain broad control of the device. It is not a remote entry point, but successful abuse could compromise sensitive data, system integrity, and availability.
Executive priority
Treat this as a high-priority remediation item because CISA identifies known exploitation and successful abuse can yield full system impact. Address affected systems promptly, especially shared endpoints and servers where an attacker could first obtain limited execution.
Technical view
CVE-2020-0638 is a local Update Notification Manager elevation-of-privilege vulnerability involving unsafe file handling, categorized as CWE-59. Exploitation requires prior execution with low privileges but no user interaction. Its CVSS 3.1 score is 7.8, with high potential impact to confidentiality, integrity, and availability.
Likely exposure
Exposure applies to the listed Windows 10 releases from versions 1709 through 1909 and specified Windows Server 2019, 1803, and 1903 installations. Systems outside the supplied affected list cannot be assessed from this evidence. Prior code execution on an affected host is required.
Exploitation context
CISA’s Known Exploited Vulnerabilities listing supports that this vulnerability has been exploited in the wild. The supplied evidence does not identify threat actors, attack campaigns, exploit availability, exploitation frequency, or the initial-access methods used before privilege escalation.
Researcher notes
The vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. CWE-59 indicates improper handling of links during file access, but the supplied sources do not provide enough technical detail to establish the precise file operation, affected component path, detection artifacts, or patch identifiers.
Mitigation direction
Inventory systems running the affected Windows and Windows Server versions.
Review Microsoft’s advisory for the applicable security update and deployment guidance.
Prioritize remediation on exposed endpoints and servers where untrusted users or code can execute.
Restrict unnecessary local execution and privileges while remediation is pending.
Validation and detection
Match operating-system versions and architectures against the supplied affected-product list.
Verify applicable update status using Microsoft’s advisory and endpoint-management records.
Confirm remediated systems no longer report the vendor-specified vulnerable update state.
Review security telemetry for unexplained privilege elevation from previously low-privileged processes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
MicrosoftWindows10 Version 1709 for 32-bit Systems, 10 Version 1803 for 32-bit Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1803 for x64-based Systems, 10 Version 1709 for ARM64-based Systems, 10 Version 1709 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based SystemsListed
MicrosoftWindows 10 Version 1903 for ARM64-based SystemsunspecifiedListed
MicrosoftWindows 10 Version 1903 for 32-bit SystemsunspecifiedListed
MicrosoftWindows 10 Version 1903 for x64-based SystemsunspecifiedListed
MicrosoftWindows Server2019, 2019 (Core installation), version 1803 (Core Installation)Listed
MicrosoftWindows Server, version 1903 (Server Core installation)unspecifiedListed
MicrosoftWindows 10 Version 1909 for 32-bit SystemsunspecifiedListed
MicrosoftWindows 10 Version 1909 for x64-based SystemsunspecifiedListed
MicrosoftWindows Server, version 1909 (Server Core installation)unspecifiedListed
MicrosoftWindows 10 Version 1909 for ARM64-based SystemsunspecifiedListed
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-59 · source CWE mapping
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.