Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2016-0099: Microsoft Windows Secondary Logon Service Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.

CVSS v3.1 (CISA ADP)
7.8
high
EPSS (exploit probability, 30 days)
37%
higher than 98.5% of all CVEs
Added to CISA KEV
2022-03-03
US federal due date 2022-03-24
Automatable (CISA SSVC)
no
technical impact: total

CVE-2016-0099 explained

CVE-2016-0099 is a privilege escalation flaw in the Secondary Logon Service of Microsoft Windows. The service does not properly process request handles, so a local user can gain higher privileges with a crafted application. CISA lists it as known exploited, including in ransomware campaigns.

Impact

An attacker who can already run code locally with low privileges can elevate their rights without user interaction. A successful attack gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system component. CISA does not consider it automatable, so each attack needs manual steps. Attackers are known to exploit it, and it has been used in ransomware campaigns.

Who is affected

The description names Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511. The CVE record itself lists no structured affected versions for Microsoft Windows, and it names no fixed version. Check the Microsoft advisory for the specific security updates that address this issue.

Written with AI from the data on this page and checked against it automatically.

Official description

The Secondary Logon Service in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 does not properly process request handles, which allows local users to gain privileges via a crafted application, aka "Secondary Logon Elevation of Privilege Vulnerability."

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2022-03-24 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for CVE-2016-0099 as described in the vendor advisory.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited and used in ransomware.
  3. Replace or upgrade Windows versions that no longer receive security updates from Microsoft.
  4. Limit local logon and code execution rights for untrusted users on affected systems.
  5. Check affected hosts for signs of compromise, such as unexpected privileged accounts or processes.

The CVE record names no fixed version, but this does not mean no fix exists. Follow CISA's required action: apply updates per vendor instructions. Use the Microsoft advisory to identify the correct update for each affected Windows version. Until patched, restrict who can log on locally and run applications on affected systems, and monitor for privilege escalation activity.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Questions about CVE-2016-0099

Can this be exploited remotely?
No. The attack vector is local. An attacker must already be able to run code on the system with low privileges, then use a crafted application to gain higher privileges.
Is CVE-2016-0099 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03 and notes known ransomware use. US federal agencies had a due date of 2022-03-24.
Which version fixes the issue?
The CVE record names no fixed version. Microsoft released security updates for this issue; consult the vendor advisory to find the update for your Windows version.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.