tag:blogger.com,1999:blog-7371094225858305730.post3489949794722147133..comments2023-11-03T14:10:57.549+03:30Comments on The way I waste my days: MS08-067S. Hamid Kashfihttp://www.blogger.com/profile/08049067812791150826noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7371094225858305730.post-26707659837225056642008-10-28T08:41:00.000+03:302008-10-28T08:41:00.000+03:30Tnx for details.Tnx for details.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7371094225858305730.post-79265769385525242432008-10-25T11:21:00.000+03:302008-10-25T11:21:00.000+03:30I had decided to write a post about this,but i saw...I had decided to write a post about this,but i saw your great post and i carefree about that.anyway thanks for your post.<BR/>as i read in SDL blog,they said neither our fuzzing test nor source code auditing wasn't successful.so how this issue found out by the malware programmer that caused Microsoft to discover that bug is another question(as said in technet blog).<BR/><BR/>you can find a copy of new semi worm/trojan(i mean Gimmiv)that released recently in the wild in below URL for analysis or something else.<BR/>http://www.offensivecomputing.net/?q=ocsearch&ocq=d65df633dc2700d521ae4dff8c393bff<BR/><BR/>I think this issue force at least some of fuzzer developer to deploy their fuzzer and fuzzing technique and libraries especially in case of MSRPC.<BR/>I'm eager to hear more news about this,may be future information clarify these questions.<BR/><BR/>cheers,sCORPINohttps://www.blogger.com/profile/09851091476158546487noreply@blogger.com