Windows COM Marshaler CVE-2017-0213
HIGHSeverity by source
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
7DescriptionCVE.org
Windows COM Aggregate Marshaler in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation privilege vulnerability when an attacker runs a specially crafted application, aka "Windows COM Elevation of Privilege Vulnerability". This CVE ID is unique from CVE-2017-0214.
AnalysisAI
Local privilege escalation in the Windows COM Aggregate Marshaler affects all Windows versions from Server 2008 SP2 through Windows 10 1703, allowing low-privileged authenticated users to gain SYSTEM-level privileges through a specially crafted application. This vulnerability is confirmed actively exploited (CISA KEV) with publicly available exploit code (Exploit-DB 42020) and an exceptionally high EPSS score of 92.69%, indicating near-certain real-world exploitation. Microsoft released patches in May 2017, but the widespread exploitation and broad platform impact make this a critical remediation priority for any unpatched Windows systems from this era.
Technical ContextAI
The Windows Component Object Model (COM) is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. The COM Aggregate Marshaler handles inter-process communication and object serialization between COM components running at different privilege levels. This vulnerability exists in the marshaler's handling of COM objects when aggregating interfaces across security boundaries. When a low-privileged process creates a specially crafted COM object and leverages the marshaler to interact with higher-privileged processes, the marshaler fails to properly validate security tokens during the aggregation process. This allows the attacker's COM object to inherit elevated privileges from the target process. The affected CPE strings span a decade of Windows releases: Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows 10 versions 1507/1511/1607/1703, Windows Server 2008 SP2 and R2 SP1, Windows Server 2012 and R2, and Windows Server 2016. The vulnerability is architectural rather than tied to a specific service, residing in core COM runtime libraries (combase.dll/ole32.dll) present across all Windows installations.
RemediationAI
Apply Microsoft's May 2017 security updates immediately via the platform-specific patches listed in security advisory CVE-2017-0213 at https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0213. For Windows 7 and Server 2008 R2 systems now past end-of-life, organizations must either purchase Extended Security Updates (ESU) from Microsoft to receive the patch, migrate to supported Windows versions (Windows 10/11, Server 2016 or later), or implement compensating controls with significant operational impact. Compensating controls for unpatchable systems include: restricting local logon rights to only essential administrative accounts via Group Policy (Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > 'Allow log on locally'), which prevents low-privileged users from executing local exploits but severely limits workstation usability; deploying application whitelisting via Windows AppLocker or third-party solutions to block unauthorized executables, though this requires extensive baseline development and ongoing maintenance; and network segmentation to isolate vulnerable systems from internet-facing assets, reducing initial access vectors but not eliminating risk from insider threats or lateral movement. None of these mitigations fully address the vulnerability - patching or replacement remains the only complete solution. Organizations maintaining legacy systems should implement multiple compensating controls in defense-in-depth layers while accelerating migration timelines given confirmed active exploitation.
Share
External POC / Exploit Code
Leaving vuln.today