Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› CVE-2019-0880 (Microsoft Windows Privilege Escalation)
Threats, Abuse & Incident Response

CVE-2019-0880 (Microsoft Windows Privilege Escalation)

← Back to Glossary
By NHI Mgmt Group Updated October 17, 2026 Domain: Threats, Abuse & Incident Response

CVE-2019-0880 is a privilege escalation vulnerability in Microsoft Windows. CISA added it to the Known Exploited Vulnerabilities catalogue on 23 May 2022, which means attackers have used it in real attacks. A local elevation of privilege vulnerability exists in how splwow64.exe handles certain calls.

What This Vulnerability Means in Practice

CVE-2019-0880 is a local privilege escalation issue in Microsoft Windows, so the core danger is that a user or process with limited access can gain higher privileges on the same system. That makes it especially valuable to an attacker who already has a foothold and wants to turn that foothold into administrative control.

The vulnerable component is splwow64.exe, a Windows process involved in handling certain calls for 32-bit and 64-bit interoperability. When that boundary is mishandled, it can become a route to execute actions with more authority than intended, which is why privilege escalation flaws often matter even when they are not remotely exploitable.

Why Local Privilege Escalation Is Dangerous

Privilege escalation turns an ordinary compromise into a much broader one. If an attacker can move from a standard user context to elevated rights, they can alter security settings, access protected data, install persistence, and sometimes disable monitoring or recovery controls.

For Windows environments, local elevation of privilege is particularly consequential because workstation compromise often becomes a stepping stone to credential theft, lateral movement, and broader domain abuse. Public vulnerability records and exploitability context are best confirmed through the NIST National Vulnerability Database and the CVE Program, which remain the authoritative references for record metadata.

How Organisations Check Exposure and Prioritise Action

Exposure review starts with identifying which Windows assets still match the vulnerable product family, then confirming where those systems sit in the environment, whether they are internet-facing through remote access paths, and whether they are used by privileged or high-value users. That inventory step matters because local escalation flaws are most dangerous where the attacker already has a user session or another initial access path.

From there, teams should compare asset scope against vendor advisories and the CISA KEV catalogue entry that marked this CVE as actively exploited. KEV inclusion is a strong signal that the issue is not just theoretical, so prioritisation should reflect real-world abuse rather than generic severity alone. For a structured remediation workflow, the Vulnerability Management Guide is useful for asset scoping, prioritisation, verification and exception handling.

Remediation, Detection, and Post-Exploitation Review

The preferred response is to apply the vendor-recommended fix as soon as practical, but when patching is delayed, compensating controls should reduce the chance of an initial foothold turning into full system control. That usually means tightening local admin access, limiting who can log on interactively, monitoring unusual parent-child process behaviour around splwow64.exe, and increasing scrutiny on endpoints where privileged users work.

After remediation, organisations should still review for signs that the vulnerability was already used. A local escalation event can leave little obvious evidence unless logging, endpoint telemetry, and privilege-change monitoring are in place, so post-patch review should look for suspicious privilege transitions, abnormal service creation, unexpected persistence, and credential access on affected hosts. The MITRE ATT&CK Enterprise Matrix is a useful reference for mapping privilege escalation, credential access, and follow-on lateral movement patterns.

Risk and Threat Considerations

This kind of flaw is attractive because it converts ordinary user access into higher privilege on the same endpoint, which can collapse the defender's trust boundary very quickly. In practice, the main risk is not just a single machine takeover, but the downstream use of that elevated position to harvest credentials, weaken controls, and expand access across the environment.

Failure mechanism: A low-privilege attacker abuses a Windows handling flaw in splwow64.exe to execute code or actions with elevated rights, bypassing the intended user boundary.

Impact: The attacker can gain administrative control on the host, access protected resources, and use the elevated session to support persistence, credential theft, or lateral movement.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5SI-2 — Flaw RemediationLocal privilege escalation demands prompt flaw remediation on Windows hosts.
AC-6 — Least PrivilegePrivilege escalation is the direct failure mode that least privilege is meant to constrain.
AU-2 — Event LoggingDetection of escalation attempts depends on logging privilege changes and suspicious process activity.
Recommendation — Track and remediate the vulnerable Windows component promptly across in-scope systems. Restrict user and service privileges so a local compromise cannot easily become admin access. Log privilege changes and endpoint activity needed to spot exploitation and post-exploitation steps.
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareWindows hardening and controlled configuration reduce exploitability and exposure surface.
CIS-7 — Continuous Vulnerability ManagementActive exploitation and KEV status make vulnerability prioritisation central to this CVE.
CIS-8 — Audit Log ManagementPrivilege escalation investigations depend on preserving logs and endpoint telemetry.
Recommendation — Harden Windows configurations and remove unnecessary exposure paths on affected endpoints. Prioritise the CVE using asset inventory, exposure, and active exploitation signals. Centralise and retain logs needed to investigate privilege escalation and follow-on activity.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org