Linked by Amjith Ramanujam on Sat 19th Jul 2008 19:01 UTC, submitted by cypress
Permalink for comment 323835
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2008-07-21
You are correct in that both ActiveX and Netscape-style plug-ins are native code that can have the same flaws.
But the main difference is the packaging and installation of that code:
With a plug-in, the installation is very obvious. A specially-formatted plug-in file needs to be put in a special location for the browser. And that process is generally done by a plug-in installer application.
With ActiveX, however, *any* Windows application is likely to install ActiveX controls. They can be in any location, and they don't even have to do anything related to your web browser. If a component is packaged up as a COM object (very common on Windows), then IE can "use" it.
http://www.kb.cert.org/vuls/id/680526
The installation of an ActiveX control can happen natively through the web browser, or through installing any application (internet-related or not). e.g. Winzip:
http://www.kb.cert.org/vuls/id/225217
The end result is that there are LOTS of systems that have LOTS of ActiveX controls that they may not even be aware of.