Dailydave mailing list archives

Re: Immunity PoC for MSDTC?


From: sinan.eren () immunitysec com
Date: Mon, 28 Nov 2005 12:33:23 -0500 (EST)


my bad!

it is the msrpc packet but the port number is all messed up.
of course! i didnt bother with all that hex stuff. thanks to the anonymous researcher for the heads up ;)

cheers,
sinan



On Sun, 27 Nov 2005 sinan.eren () immunitysec com wrote:


printf("Default port: 3372\n");

this is the idefense TIP DoS. not the msrpc vector.
complete different story ...

-sinan

On Sun, 27 Nov 2005, Dave Aitel wrote:

If my quick read is correct, this is a different issue from the one we exploited. One patch, many bugs. I think we thought the other vulnerability was more exploitable than this one, even if it has reliability issues.

-dave

Andrew Simmons wrote:
http://www.securityfocus.com/bid/15056/exploit :

"Microsoft Windows MSDTC Memory Corruption Vulnerability

"Reports indicate that Immunity has developed a proof of concept exploit for this issue."

[...]

/*
\ MSDTC remote PoC exploit
/ by Darkeagle
\
/
\ Unl0ck Research Team
/
\
/ Greetingz: all UKT boys, 0x557 guys, Sowhat, GHC/RST guys
\
/ Exploit tested on: Windows 2000 Professional Russian Service Pack 4
\


Hmmmm!


\a






Current thread: