I was able to easily plant a backdoor using the EternalBlue tool, but the DoublePulsar implant was not developed with Windows Embedded 7 in mind and exploit attempts would throw an error upon execution: I then figured I’d go straight to the Fuzzbench framework which I know works against x86 devices. I finally found that it has only been ported to 圆4 at this time, and the authors clearly state that attempts to exploit an x86 device will crash it. I first tried using the exploit/windows/smb/ms17_010_eternalblue Metasploit module, but each attempt resulted in a blue screen no matter which payload I tried. I found the following posts especially helpful as I worked through this exercise, so many thanks to the authors! I needed to do some tweaking to get the current tools to work, but in the end, the attack worked as expected and probably will continue to work for a long time given the general lack of patching of embedded devices. I am nearing completion of a very long and complex pen test of an environment made up completely of networked embedded devices, so when the Equation Group’s Fuzzbunch framework was released publicly, I figured it would be perfect for a few boxes I was struggling to gain complete access to. While much of the focus has been on patching desktops and servers, it’s easy for many organizations to continue to neglect devices running the Windows Embedded 7 OS.
#WINDOWS XP EMBEDDED PATCHES UPDATE#
MS17-010 and has fortunately resulted in organizations applying the security update to prevent further infections. The recent wave of WannaCry ransomware attacks has shed a lot of public light on the Windows SMB remote code execution vulnerability patched by