Windows Wi-Fi Code Execution Flaw Let Attacker Hijack Your Devices

Microsoft patched loads of vulnerabilities as section of June 2024’s Patch Tuesday, one of which was associated to remote code execution in Wi-Fi Driver.

This vulnerability was assigned with CVE-2024-30078, and the severity was 8.8 (High).

Alternatively, according to Microsoft’s description of this vulnerability, it must also merely furthermore be considered that it would now not require user interplay.

Microsoft acknowledged that this vulnerability is now not known to be exploited within the wild. Alternatively, it is miles that you could perhaps perhaps imagine that it could perhaps perhaps easily attract possibility actors.

Technical Prognosis

In accordance with the advisory, this vulnerability requires the possibility actor to be linked to the identical network as the susceptible device and in a living to ship and gain radio transmissions.

To use this vulnerability, the possibility actor must ship malicious networking to the affected Wi-Fi adapter, that will raise out remote code on the machine.

Further, the possibility actor would now not require authentication, which makes it extremely easy to make the most of. Wei reported this vulnerability in Kunlun Lab with Cyber KunLun.

This vulnerability would now not require any special prerequisites or conditions to make the most of. Alternatively, this vulnerability affects the next Microsoft Merchandise.

• Windows Server 2012 R2 (Server Core installation)
• Windows Server 2012 R2
• Windows Server 2012 (Server Core installation)
• Windows Server 2012
• Windows Server 2008 R2 for x64-essentially based mostly Programs Carrier Pack 1 (Server Core installation)
• Windows Server 2008 R2 for x64-essentially based mostly Programs Carrier Pack 1
• Windows Server 2008 for x64-essentially based mostly Programs Carrier Pack 2 (Server Core installation)
• Windows Server 2008 for x64-essentially based mostly Programs Carrier Pack 2
• Windows Server 2008 for 32-bit Programs Carrier Pack 2 (Server Core installation)
• Windows Server 2008 for 32-bit Programs Carrier Pack 2
• Windows Server 2016 (Server Core installation)
• Windows Server 2016
• Windows 10 Version 1607 for x64-essentially based mostly Programs
• Windows 10 Version 1607 for 32-bit Programs
• Windows 10 for x64-essentially based mostly Programs
• Windows 10 for 32-bit Programs
• Windows Server 2022, 23H2 Edition (Server Core installation)
• Windows 11 Version 23H2 for x64-essentially based mostly Programs
• Windows 11 Version 23H2 for ARM64-essentially based mostly Programs
• Windows 10 Version 22H2 for 32-bit Programs
• Windows 10 Version 22H2 for ARM64-essentially based mostly Programs
• Windows 10 Version 22H2 for x64-essentially based mostly Programs
• Windows 11 Version 22H2 for x64-essentially based mostly Programs
• Windows 11 Version 22H2 for ARM64-essentially based mostly Programs
• Windows 10 Version 21H2 for x64-essentially based mostly Programs
• Windows 10 Version 21H2 for ARM64-essentially based mostly Programs
• Windows 10 Version 21H2 for 32-bit Programs
• Windows 11 version 21H2 for ARM64-essentially based mostly Programs
• Windows 11 version 21H2 for x64-essentially based mostly Programs
• Windows Server 2022 (Server Core installation)

Microsoft furthermore specified that there will not be any publicly on hand exploit for this vulnerability. Mute, purposeful reproduction is that you could perhaps perhaps imagine, and source code is on hand to independently examine the research’s assertions.

How To Substitute And Fix This Vulnerability?

To update your Windows, Sprint to Originate Menu → Settings → Substitute & Security → Test for Updates.

In case your Windows has now not reached Discontinuance-of-Life, you could perhaps perhaps gain the updates, along side the patch for this Wi-Fidriver vulnerability. Inserting within the updates will repair this vulnerability to your machine.