CVE-2019-0943

Windows ALPC Elevation of Privilege Vulnerability

N/A
Published: June 12, 2019 at 01:49 PM UTC
Updated: June 17, 2026 at 02:09 AM UTC
17 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1703 by Microsoft?

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

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%

Description

An elevation of privilege vulnerability exists when Windows improperly handles calls to Advanced Local Procedure Call (ALPC). An attacker who successfully exploited this vulnerability could run arbitrary code in the security context of the local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. 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 over an affected system. The update addresses the vulnerability by correcting how Windows handles calls to ALPC.

Affected

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

10.0.0 ≤ v < publication160717031709180318091903
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.10240.0 ≤ v < publication10.0.10240.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.14393.0 ≤ v < publication10.0.14393.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.17763.0 ≤ v < publication10.0.010.0.17763.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.1.0 ≤ v < publication6.1.0sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.3.0 ≤ v < publication6.3.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
6.1.0 ≤ v < publication6.1.7601.0 ≤ v < publication6.1.06.1.7601.0r2 sp1
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:

CVSS

Confidentiality
COMPLETE
Integrity
COMPLETE
Availability
COMPLETE
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