More on MS08-008
For the past week I have been looking at the MS08-008 OLE remote execution vulnerability. During that time, I have been speaking with an exploit writer who wishes to remain anonymous. According to my anonymous source, the vulnerability exists within the ActiveX class MSForms Image and uses the IImage Interface. As the vulnerability requires user intervention and can easily be thwarted by setting the kill bit, my source does not believe that this will be very useful in targeted attacks.
According to Microsoft, Visual Basic (VB) 6.0 contains this vulnerability. Programs created in VB 6.0 may inherit the vulnerability if the oleaut32.dll file is distributed with the VB 6.0 created programs. I installed many free OPC servers, OPC clients and OPC utilities and I found the oleaut32.dll file in one piece of software. The oleaut32.dll file in the software was not installed on the system as the file was designed for Windows 95/NT and the test system was running Windows 2003 R2 Service Pack 2.
The best course of action is to set the kill bit and perform an update to your system as soon as possible. Setting the kill bit, see the MS08-008 page for instructions, should provide adequate protection while the patches are being vetted for production use. It would be wise to search the system for “oleaut32.dll” to determine if there are other copies of this file, possibly installed by a vendor, on your system. Please contact your vendor if you are concerned that they are distributing a vulnerable version of the oleaut32.dll file.
The likelihood that this vulnerability is exploitable in OPC software is low. Please take the appropriate actions to mitigate this vulnerability in your environment and reduce your attack surface.
Author: Charles Perine
Posted: February 20th, 2008 under Microsoft.
Comments: 2
Comments
Comment from stacy
Time: February 21, 2008, 12:30 pm
It is worth noting that a Kill-Bit is, as the joke goes, only a suggestion. The application has to check and honour the Kill-Bit, setting the Kill-Bit does not guarantee that the vulnerable control can not be instantiated.
There was a three part FAQ on Kill-Bits posted to MS Security Vulnerability Research & Defense blog. http://blogs.technet.com/swi/
Comment from Daniel
Time: February 21, 2008, 6:14 pm
stacy is right, but as the most likely vector for this is IE, so the killbit workaround should be effective.
If a 3rd party app is the vector for this attack, and it doesnt check the status of killbit in the registry then there are likely numerous other ways that it will be vulnerable to attack.
Best practices are just that, and cannot completely overcome insecure code.
Write a comment