MS17-010 Vulnerability - New EternalBlue SMB module for Metasploit - Exploiting Windows 8.1

In its July 2018 update, Metasploit has released a new EternalBlue module named: ms17_010_eternalblue_win8   The short description for this module reads: MS17-010 EternalBlue SMB remote Windows Kernel Pool Corruption for Win8+
The July Metasploit update releases can be found on this link.

Of course, Metasploit already had an EternalBlue module which was called ms17_010_eternalblue, but this older module was compatible only with Windows 7 and Windows 2008 R2 (x64).
On the other hand, the new ms17_010_eternalblue_win8 is listed as being compatible with Windows 8.1, Windows 10 (selected builds) and Windows 2012 R2 (x64).

Before watching my new video on exploiting Windows 8.1 with the new ms17_010_eternalblue_win8 module, you might find useful reviewing my previous posts related to the EternalBlue exploit, which I list below:

1.  MS17-010 Vulnerability - Using EternalBlue exploit module in Metasploit

2. MS17-010 Vulnerability - EternalBlue exploit using a binary payload and python script on Windows 7 and Windows 2008 R2 targets



Also, if you want to test the new EternalBlue module into your own lab, then make sure that you update your Kali Linux installation first. The ms17_010_eternalblue_win8 module will be installed during the Kali update process. If you need help updating your Kali Linux machine, then check the following post: Installing Kali Linux as a VMware Virtual Machine

MS17-010 EternalBlue SMB remote Windows Kernel Pool Corruption for Win8+ Metasploit Module

exploit/windows/smb/ms17_010_eternalblue_win8


MS17-010 Vulnerability - New EternalBlue SMB module for Metasploit - Exploiting Windows 8.1



Note:

 During the last couple of weeks I have tested the ms17_010_eternalblue_win8 module against multiple Windows 10 build versions as well as against Windows 2012 R2. At this stage, I haven't been able to successfully exploit Windows 10 nor Windows 2012 R2, even if the module description said that it should have worked.

So far, I have had the following experience with the various Windows 10 (x64) build versions:
- Win10 Pro             Build 10240           - The target machine crashed
- Win10 Pro             Build 10586.0        - The target machine crashed
- Win10 Enterprise Build 10586.0        - The target machine crashed
- Win10 Pro             Build 10586.164   - The target machine crashed
- Win10 Pro             Build 14393.0        - This exploit doesn't support build 14393 or above

As a workaround, I have tried to lower the GroomAllocations ( numGroomConn ) parameter value, but the Windows 10 target machine kept crashing.

On the other hand, when I attempted to use the module against my Windows 2012 R2 (Build 9600) test machine, the module gave the following error:
 'ascii' codec can't decode byte 0xc5 in position 2: ordinal not in range(128)


I'll update this post when I'm able to use the ms17_010_eternalblue_win8 module against other OSes. 

Comments

Post a comment

Popular Posts

MS17-010 Vulnerability - Using EternalBlue exploit module in Metasploit

Generating shellcode - using msfvenom to generate a binary payload

MS17-010 Vulnerability - Scanning using Metasploit on KALI Linux