 |
 |
|
December 30, 2005Are you WMF'd to death yet?Wondering why you haven't seen any feedback from me on the most recent 0-day exploit on Windows, which takes advantage of a vulnerability in the graphics rendering engine? I took a vacation away from the computer for a few days to catch up on some technical reading, and come back to a plethora of information that pretty much sums up anything I would say. In a blog post in the next few days, I will post just WHAT I was reading, as its pretty interesting. I'm shaking my head as I absorb some of this new stuff. Anyways, as a summary of the past few days where the world has been screaming that the sky is falling, here is the nitty gritty that matters (at least from my POV)
I disagree with Susan that it is too drastic to unregister the DLL. It's quite trival a fix to signficantly mitigate against this threat without impacting the rest of the system. So you don't get pretty thumbnails. But you do prevent the exploit through this attack vector (I will point out it won't stop against someone opening an exploited WMF in MS Paint etc). And with the ability to push this out to all the desktops pretty quickly with a script... it takes no time to toggle it on/off. YMMV of course. That's pretty much all you will hear from me on the WMF issue for now. You can read the other 1,000,000 blog posts about it for more information. Posted by SilverStr at December 30, 2005 03:29 PM | TrackBackComments
I wonder how many people have sort of missed out on this, since it happened over the holidays. I've been OOO for a week, as have quite a few people at my office. I wonder if IT organizations have the horsepower to roll out the fix you describe due to short staffing. This makes a pretty good case for hardware DEP, at least for now (I feel sure someone will find a way around it soon). Posted by: Steve Dispensa at December 30, 2005 04:16 PMAny ideas on how to unregister the DLL using group policy? Peter, The quickest way to do it through GPO might be to add a startup script in the "Scripts" section of the Windows Settings for Computer Configuration of your policy. If you google for "GPO startup scripts" you should find enough information on how to set this up. I haven't tried this method, but it would seem to be the fastest method. YMMV of course. Posted by: Dana Epp at January 2, 2006 02:26 AMI put together a short login script to that will unregister the DLL, and then install the unofficial patch that was released by hexblog.com, if you havn't already installed it. If you'd just prefer to unregister the DLL, then you can delete the extra stuff in the script and use it as a login or GPO startup script. Check it out; http://addicted-to-it.blogspot.com/2006/01/patching-script-to-deploy-unofficial.html |
 
My 5 Favorite Books
Writing Secure Code
Secure Programming Cookbook Security Engineering Secure Coding Principles & Practice Inside the Security Mind
My 5 Favorite Papers
Smashing the Stack
Penetration Studies Covert Channel Analysis of Trusted Systems DoD Trusted Computer System Evaluation Criteria NSA Security Recommendation Guides
Archives
January 2007
December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 |
|
