Local Rpc Dcom Overflow

GovernmentSecurity.org > System Security > Beginners Section

MxMx

Aug 26 2004, 03:23 PM

hey all..

Ive finally figured a way out to exploit some server in my own network

I use the original RPC DCOM Universal exploit and I first did a local scan to check the pcs in my network. Scanms found 5 servers [vuln] [vuln].. so I tried to exploit them but it cant connect:S..
whats the port I should let netcat listen to or mustn't I use netcat..
anyone can help me out please

thanks

mandawar

Aug 26 2004, 03:52 PM

QUOTE (MxMx @ Aug 26 2004, 03:23 PM)

hey all..

Ive finally figured a way out to exploit some server in my own network

thanks

exploit some server in my own network >>

i prefer you should try the LSASS Exploit... and yes you need netcat

Antil

Aug 26 2004, 04:13 PM

finding vulnr servers in the network doesnt mean you can exploit them.. most show as vulnr but only few you get a shell..

once you open and start the prog it should have actually asked you for the netcat port you opened to get the shell on... dunno why it didnt for you

BBQ CD

Aug 27 2004, 11:37 AM

check that your shells has no bindport error while executing the exploit ...

You said that you are using a "local" exploit, means that it only your local box, not a remote!

andydis

Aug 27 2004, 01:53 PM

QUOTE

I use the original RPC DCOM Universal exploit

the very first rpc exploits where flaky at best,

some even shit down computers rather than giving out shells depending what offsets you used.

if i where u id get another version of the exploit (more up to date and has more options).

or as above try lsass.

whats youre server running? and is it fully windows updated?
what did u scan them with do show these vuln?

beucase even eeye's software says ppl are vuln when they are not (simply becuase they have port 139 open)

just do some more research and youll be kewl mate

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.