CVE-2016-3309
Published: March 15, 2022
Official Description
A privilege escalation vulnerability exists when the Windows kernel fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode.
CISA KEV Advisory
Microsoft Windows Kernel Privilege Escalation Vulnerability
A privilege escalation vulnerability exists when the Windows kernel fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode.
Apply updates per vendor instructions.
Risk Analysis
A privilege escalation vulnerability exists in the Windows kernel due to improper handling of objects in memory, allowing an attacker to run arbitrary code in kernel mode. The high EPSS score of 0.45234 indicates a significant likelihood of exploitation, and its presence in the KEV catalog confirms it has been actively exploited.
This vulnerability has been actively exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog. Exploitation typically requires local access.
Apply all available security updates for Microsoft Windows. Implement the principle of least privilege to limit the impact of successful privilege escalation attempts.
Technical Analysis
CVE-2016-3309 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2016-3309 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2016-3309 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1