ADV230001 — Guidance on Microsoft Signed Drivers Being Used Maliciously
Executive Summary
Microsoft was recently informed that drivers certified by Microsoft’s Windows Hardware Developer Program (MWHDP) were being used maliciously in post-exploitation activity. In these attacks, the attacker gained administrative privileges on compromised systems before using the drivers. Microsoft has completed its investigation and determined that the activity was limited to the abuse of several developer program accounts and that no Microsoft account compromise has been identified. We’ve suspended the partners' seller accounts and implemented blocking detections for all the reported malicious drivers to help protect customers from this threat. Details: Microsoft was informed that drivers certified by Microsoft’s Windows Hardware Developer Program were being used maliciously in post-exploitation activity. In these attacks, the attacker had already gained administrative privileges on compromised systems prior to use of the drivers. An investigation was performed when we were notified of this activity by Sophos on February 9, 2023; Trend Micro and Cisco subsequently provided reports containing additional details. This investigation revealed that several developer accounts for the Microsoft Partner Center (MPC) were engaged in submitting malicious drivers to obtain a Microsoft signature. All the developer accounts involved in this incident were immediately suspended. Microsoft has released Window Security updates (see Security Updates table) that untrust drivers and driver signing certificates for the impacted files and has suspended the partners' seller accounts. Additionally, Microsoft has implemented blocking detections (Microsoft Defender 1.391.3822.0 and newer) to help protect customers from legitimately signed drivers that have been used maliciously in post-exploit activity. For more information about how the Windows Code Integrity feature protects Microsoft customers from revoked certificates see: (Notice of additions to the Windows Driver.STL revocation list - Microsoft Support)[https://support.microsoft.com/help/5029033]. Microsoft is working with Microsoft Active Protections Program (MAPP) partners to help develop further detections and to better protect our shared customers. Microsoft Partner Center is also working on long-term solutions to address these deceptive practices and prevent future customer impacts. Microsoft recommends that all customers install the latest Windows updates and ensure their anti-virus and endpoint detection products are up to date with the latest signatures and are enabled to prevent these attacks. Are any Microsoft services (Azure, M365, XBOX, Etc.) affected by this issue? Microsoft’s services are not affected by this issue. Our investigation has not identified any instances of malicious drivers affecting any of our services. How can customers deploy their own Hypervisor-protected Code Integrity (HVCI) policy to perform detections in their own environment? Updates will be made to the Microsoft Recommended Driver Blocklist - Microsoft recommended driver block rules (Windows 10) - Windows security | Microsoft Docs policy to perform detections in their own environment. After the full set of malicious files has been locked, customers (enterprise and consumer) can deploy this policy onto devices to block against this malicious file and other malicious and vulnerable drivers on the blocklist. Additionally, enabling Hypervisor-protected Code Integrity (HVCI) will automatically enforce the policy without needing to deploy the policy. How do I determine if any drivers are affected that were installed prior to the available detections were implemented? Offline scans will be required to detect malicious drivers which might have been installed prior to March 2, 2023, when new Microsoft detections were implemented. For more information see Remove malware from your Windows PC .
Overview
EPSS Score
No EPSS score available for this CVE.
View on FIRST.orgAffected Products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Windows 10 for 32-bit Systems | 5029259 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 for x64-based Systems | 5029259 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 1607 for 32-bit Systems | 5029242 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 1607 for x64-based Systems | 5029242 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 5029247 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 1809 for ARM64-based Systems | 5029247 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 1809 for x64-based Systems | 5029247 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5029244 (Security Update) |
None | Defense in Depth | Yes |
| Windows 11 version 21H2 for ARM64-based Systems | 5029253 (Security Update) |
None | Defense in Depth | Yes |
| Windows 11 version 21H2 for x64-based Systems | 5029253 (Security Update) |
None | Defense in Depth | Yes |
| Windows 11 Version 22H2 for ARM64-based Systems | 5029263 (Security Update) |
None | Defense in Depth | Yes |
| Windows 11 Version 22H2 for x64-based Systems | 5029263 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 5029318 (Monthly Rollup) 5029301 (Security Only) None Defense in Depth 5028222 Base: N/A Temporal: N/A Vector: N/A 6.0.6003.22216 Yes 5029318 5029301 Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) 5029318 (Monthly Rollup) 5029301 (Security Only) None Defense in Depth 5028222 Base: N/A Temporal: N/A Vector: N/A 6.0.6003.22216 Yes 5029318 5029301 Windows Server 2008 for x64-based Systems Service Pack 2 5029318 (Monthly Rollup) 5029301 (Security Only) None Defense in Depth 5028222 Base: N/A Temporal: N/A Vector: N/A 6.0.6003.22216 Yes 5029318 5029301 Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) 5029318 (Monthly Rollup) 5029301 (Security Only) None Defense in Depth 5028222 Base: N/A Temporal: N/A Vector: N/A 6.0.6003.22216 Yes 5029318 5029301 Windows Server 2008 R2 for x64-based Systems Service Pack 1 5029296 (Monthly Rollup) 5029307 (Security Only) None Defense in Depth 5028240 Base: N/A Temporal: N/A Vector: N/A 6.1.7601.26664 Yes 5029296 5029307 Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) 5029296 (Monthly Rollup) 5029307 (Security Only) None Defense in Depth 5028240 Base: N/A Temporal: N/A Vector: N/A 6.1.7601.26664 Yes 5029296 5029307 Windows Server 2012 5029295 (Monthly Rollup) 5029308 (Security Only) None Defense in Depth 5028232 Base: N/A Temporal: N/A Vector: N/A 6.2.9200.24414 Yes None Windows Server 2012 (Server Core installation) 5029295 (Monthly Rollup) 5029308 (Security Only) None Defense in Depth 5028232 Base: N/A Temporal: N/A Vector: N/A 6.2.9200.24414 Yes None Windows Server 2012 R2 5029312 (Monthly Rollup) 5029304 (Security Only) None Defense in Depth 5028228 Base: N/A Temporal: N/A Vector: N/A 6.3.9600.21503 Yes None Windows Server 2012 R2 (Server Core installation) 5029312 (Monthly Rollup) 5029304 (Security Only) None Defense in Depth 5028228 Base: N/A Temporal: N/A Vector: N/A 6.3.9600.21503 Yes None Windows Server 2016 | 5029242 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2016 (Server Core installation) | 5029242 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2019 | 5029247 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2019 (Server Core installation) | 5029247 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2022 | 5029250 (Security Update) |
None | Defense in Depth | Yes |
| Windows Server 2022 (Server Core installation) | 5029250 (Security Update) |
None | Defense in Depth | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5029259 |
Security Update | Yes |
5029242 |
Security Update | Yes |
5029247 |
Security Update | Yes |
5029244 |
Security Update | Yes |
5029253 |
Security Update | Yes |
5029263 |
Security Update | Yes |
5029250 |
Security Update | Yes |
Known Exploits
Acknowledgments
Sophos X-Ops teams, Chris Neal of Cisco Talos, Trend Micro Research