Oh Boy....
Look, ActiveX is just a COM Client. It is one [and I think good] method of remote invocation [it was designed to allow for code validation and signing]. Any method of RMI - CORBA, Java RMI, DCOM, etc... has its vulnerabilities - a lot of them. If you think ActiveX is bad...well, please look at SUN RPC on 111 before you comment or the comments opposite Mozilla, which is a huge part of Firefox...
The update provided yesterday adjusts how such remoting is handled within the LMZ on a system. It is very similar to the many changes made opposite the handling of ActiveX coontrols [COM Cliency] in XP SP2 and W2K3, its SP1 and later, its R2.
Two things, 1) Set up whatever profile/configuration you like in W2K and XP - once set up, create a new user with limited rights on the LMZ. Copy the profile you created over the new limited user; verify that the new user is restricted and run as that user, only. If you need to install SW, use the "RUN AS" option - in other words, control your machine and take ownership of it. Either that, or use RUN AS each time you want to install SW and simply run as a restricted user - or wait around for MS to hold your hand and release SP2...
2) Look real hard at just how bad Mozilla and Forefox are from a security standpoint - for that matter, Minuces and Linuces, too and at just how many are rooted to the hilt - it is a lot easier than you think - particularly since the source is open and essentially always has been.
The USNSA has warned all in Govt. about this for years, and even released its own hardened version to offset native vulnerabilities. The truth is, MS writes the most secure code available -despite the noise we all hear. I will say only this...there are a great number of professionals very glad that so many blindly put their faith is such systems. Thanks for the ear.
|