LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1064: Windows Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links. An attacker who successfully exploited this vulnerability could run processes in an elevated context. An attacker could then install programs; view, change or delete data. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The security update addresses the vulnerability by correcting how Windows AppX Deployment Service handles hard links.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-1064 lets a logged-in attacker gain higher privileges on affected Windows systems. The flaw is in how the Windows AppX Deployment Service handles hard links. If exploited, it could allow installing programs or viewing, changing, or deleting data. CISA lists it as known exploited, so unresolved exposure should be treated as urgent.

Executive priority

High priority for any remaining affected Windows assets. This is not remotely exploitable by itself, but it is a proven exploitation target that can turn a low-privilege foothold into elevated control. Prioritize internet-facing support systems, shared workstations, and servers where users or service accounts can log on.

Technical view

This is a local Windows elevation-of-privilege issue in AppXSVC, mapped to CWE-59. Exploitation requires local logon and running a crafted application. Successful exploitation runs processes in an elevated context. Microsoft rates it CVSS 3.1 7.8 with low attack complexity, low privileges required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on unpatched affected Windows 10 versions 1607 through 1903, Windows Server 2016, Windows Server 2019, and listed Server Core installations. Systems that allow broad interactive logon or unmanaged application execution carry higher practical risk.

Exploitation context

Active exploitation is supported by CISA KEV inclusion. The provided sources do not describe exploit scale, attacker groups, or public weaponization details. Because the attack requires local access, this is most dangerous after phishing, stolen credentials, malware execution, or other initial access.

Researcher notes

Evidence supports a local EoP via improper hard-link handling in AppXSVC. The source bundle confirms Microsoft update availability and KEV status, but does not include detailed exploit mechanics or observed campaign data. Avoid assuming unsupported Windows versions or mitigations beyond Microsoft guidance and standard local-execution controls.

Mitigation direction

  • Apply the relevant Microsoft security update for each affected Windows version.
  • Prioritize remediation because CISA lists CVE-2019-1064 in KEV.
  • Check MSRC guidance for exact affected builds and update requirements.
  • Limit local logon rights on servers and privileged workstations.
  • Use application control where feasible to reduce untrusted local execution.

Validation and detection

  • Inventory Windows 10 and Windows Server builds against the MSRC affected list.
  • Verify the applicable Microsoft security update is installed on each affected host.
  • Confirm vulnerability scanner findings are cleared after patch deployment.
  • Review endpoint telemetry for suspicious local privilege escalation behavior.
  • Track remediation status separately for Server Core systems.
Prepared
Confidence
high
Sources
5

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.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1064 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2019-1064Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 170310.0.0Listed
MicrosoftWindows 10 Version 180310.0.0Listed
MicrosoftWindows Server, version 1803 (Server Core Installation)10.0.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 180910.0.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows 10 Version 1709 for 32-bit Systems10.0.0Listed
MicrosoftWindows 10 Version 170910.0.0Listed
MicrosoftWindows 10 Version 1903 for 32-bit Systems10.0.0Listed
MicrosoftWindows 10 Version 1903 for x64-based Systems10.0.0Listed
MicrosoftWindows 10 Version 1903 for ARM64-based Systems10.0.0Listed
MicrosoftWindows Server, version 1903 (Server Core installation)10.0.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
Weakness

CWE details

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.