Comments on: Potential Microsoft Works ActiveX Zero-Day Surfaces http://blogs.mcafee.com/mcafee-labs/potential-microsoft-works-activex-0-day-surfaces Sat, 12 May 2012 04:55:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ping.pong http://blogs.mcafee.com/mcafee-labs/potential-microsoft-works-activex-0-day-surfaces/comment-page-1#comment-16169 ping.pong Sun, 08 Jun 2008 13:36:48 +0000 http://www.labs.com/research/blog/?p=615#comment-16169 hey, I wanna know how to execute ClassId.cs script, and make it run and check the "clsid:00E1DB59-6EFD-4CE7-8C0A-2DA3BCAAD9C6". I did try with "cscs.exe" but its shooting me the error : ---- C# Script execution engine. Version 2.1.0.0. Copyright (C) 2004-2008 Oleg Shilo. Error: Specified file could not be executed. Cannot find entry point. Make sure script file contains methos: 'public static Main(...)' ----- Thanks! hey, I wanna know how to execute ClassId.cs script, and make it run and check the “clsid:00E1DB59-6EFD-4CE7-8C0A-2DA3BCAAD9C6″.
I did try with “cscs.exe” but its shooting me the error :
—-
C# Script execution engine. Version 2.1.0.0.
Copyright (C) 2004-2008 Oleg Shilo.

Error: Specified file could not be executed.

Cannot find entry point. Make sure script file contains methos: ‘public static Main(…)’
—–
Thanks!

]]> By: wsn1983 http://blogs.mcafee.com/mcafee-labs/potential-microsoft-works-activex-0-day-surfaces/comment-page-1#comment-16168 wsn1983 Fri, 18 Apr 2008 18:40:24 +0000 http://www.labs.com/research/blog/?p=615#comment-16168 :) Just for fun.For the first time of public M$ 0DAY :) Just for fun.For the first time of public M$ 0DAY

]]> By: MAxi http://blogs.mcafee.com/mcafee-labs/potential-microsoft-works-activex-0-day-surfaces/comment-page-1#comment-16166 MAxi Fri, 18 Apr 2008 13:03:07 +0000 http://www.labs.com/research/blog/?p=615#comment-16166 A few days ago I blogged about a new Word vulnerability that was used in a targeted attack (I know, it’s hard to keep these straight). Later that day Microsoft stated that the vulnerability was limited to denial of service, rather than remote code execution, and the blog was updated accordingly. A few days ago I blogged about a new Word vulnerability that was used in a targeted attack (I know, it’s hard to keep these straight). Later that day Microsoft stated that the vulnerability was limited to denial of service, rather than remote code execution, and the blog was updated accordingly.

]]>