CVE-2024-30078: Windows Wi-Fi Driver Remote Code Execution via Adjacent Network
Detects exploitation attempts of CVE-2024-30078, a critical Windows Wi-Fi Driver vulnerability (CWE-591: Sensitive Data Storage in Improperly Locked Memory) that allows unauthenticated remote code execution from an adjacent network. An attacker within Wi-Fi range can send specially crafted network packets to trigger memory corruption in the Windows Wi-Fi driver (nwifi.sys), potentially gaining SYSTEM-level code execution without user interaction. Affected platforms include Windows 10, Windows 11, and Windows Server 2008 through 2022.
Vulnerability Intelligence
TheoreticalAffected Software
- Vendor
- Microsoft
- Product
- Windows, Windows Wi-Fi Driver
- Versions
- Windows 10, Windows 11, Windows Server 2008-2022
Weakness (CWE)
Timeline
- Disclosed
- June 11, 2024
- Patched
- June 11, 2024
References & Proof of Concept
CVSS
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
What is CVE-2024-30078 CVE-2024-30078: Windows Wi-Fi Driver Remote Code Execution via Adjacent Network?
CVE-2024-30078: Windows Wi-Fi Driver Remote Code Execution via Adjacent Network (CVE-2024-30078) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for CVE-2024-30078: Windows Wi-Fi Driver Remote Code Execution via Adjacent Network, covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, Microsoft Sentinel, Windows Event Logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
let timeWindow = 1h;
let suspiciousDriverEvents = DeviceEvents
| where Timestamp > ago(timeWindow)
| where ActionType in ("DriverLoad", "ServiceInstalled")
| where InitiatingProcessFileName =~ "nwifi.sys" or FileName =~ "nwifi.sys"
| project Timestamp, DeviceId, DeviceName, ActionType, FileName, InitiatingProcessFileName, InitiatingProcessCommandLine;
let wifiCrashEvents = DeviceEvents
| where Timestamp > ago(timeWindow)
| where ActionType == "ProcessCrashed" or ActionType == "KernelPanicDetected"
| where InitiatingProcessFileName has_any ("wlanext.exe", "nwifi.sys", "wlansvc.dll")
| project Timestamp, DeviceId, DeviceName, ActionType, InitiatingProcessFileName;
let unexpectedNetworkSpawn = DeviceProcessEvents
| where Timestamp > ago(timeWindow)
| where InitiatingProcessFileName =~ "svchost.exe"
| where InitiatingProcessCommandLine has "wlansvc"
| where FileName in~ ("cmd.exe", "powershell.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe")
| project Timestamp, DeviceId, DeviceName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, AccountName;
union suspiciousDriverEvents, wifiCrashEvents, unexpectedNetworkSpawn
| extend AlertReason = case(
ActionType == "DriverLoad" and FileName =~ "nwifi.sys", "Suspicious Wi-Fi driver reload",
ActionType == "ProcessCrashed" and InitiatingProcessFileName has "nwifi", "Wi-Fi driver crash - possible exploitation attempt",
FileName in~ ("cmd.exe", "powershell.exe"), "Unexpected shell spawned from Wi-Fi service context",
"Anomalous Wi-Fi driver activity"
)
| order by Timestamp desc Detects suspicious Windows Wi-Fi driver activity indicative of CVE-2024-30078 exploitation: driver reloads, crashes in nwifi.sys context, and unexpected process spawning from the WLAN service (wlansvc). Combines DeviceEvents and DeviceProcessEvents to surface both kernel-level anomalies and post-exploitation lateral movement.
Data Sources
Required Tables
False Positives
- Legitimate Wi-Fi driver updates or reinstallations by IT administrators
- System administrators running diagnostic tools against wireless interfaces
- Antivirus or EDR products scanning nwifi.sys during scheduled scans
- Windows Update installing legitimate Wi-Fi driver patches
- Third-party wireless management software interacting with WLAN service
Sigma rule & cross-platform mapping
The detection logic for CVE-2024-30078: Windows Wi-Fi Driver Remote Code Execution via Adjacent Network (CVE-2024-30078) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: process_creation
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2024-30078
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate WLAN Service Child Process Spawn (Post-Exploitation Indicator)
Expected signal: Sysmon EventID 1 (Process Create) with ParentImage=svchost.exe, ParentCommandLine containing '-k wlansvc', Image=cmd.exe. MDE DeviceProcessEvents showing InitiatingProcessCommandLine with 'wlansvc'.
- Test 2Wi-Fi Driver Version Audit for Vulnerability Assessment
Expected signal: DeviceEvents with ActionType=FileRead on nwifi.sys path. PowerShell script block logging (EventID 4104) capturing the enumeration commands. WMI activity logs showing Win32_SystemDriver query.
- Test 3Adjacent Network Malformed 802.11 Frame Injection (Controlled Lab)
Expected signal: On the target Windows host: Windows Event Log System EventID 41 or 1001 (BugCheck/kernel crash) if exploitation succeeds. Network capture on the target side shows malformed 802.11 frames from attacker MAC. Defender/EDR may log driver fault events referencing nwifi.sys.
Unlock Pro Content
Get the full detection package for CVE-2024-30078 including response playbook, investigation guide, and atomic red team tests.