Mozilla, FireFox, Opera - they all can use COM Clients and they can and are all exploitable. I happen to be of the assessment [note I did not say belief], that alternative browsers are very
vulnerable. Oh, and in the case of most of these, they can also use ActiveX as a COM Client - on emay add it at will - just as they'd any any plug-in. I note the FF crowd in particular is fond of speaking to how many are available - they do however fail to note that ActiveX is one of them, or that one form or another is required when they do add plug-ins - I mean, how else is remote code execution to be enabled...??? I could go on for days about this, but know it might not actually help. I do hope people will explore this and really get to know how things are done. Remember, the guys and gals in the press have a different perspective - they do not build SW, HW or integrate them - they simply observe and often write about much they do not understand. I mean, simple things like Session_OnEND events and Application_OnEND Events don't even exist in FF, Moz, or Safari... only in IE, and if one does not understand why that matters, they should probably read more and post a lot less. ...ever need to fire event triggers in an app when a person dumps their browser vice exiting a session within your app? or sense when a browser or system crashes? It matters and matters a lot.
Trust me, if there were a browser war, and MS wanted to fight it, it'd be like the 82nd AB Div picking on a cub-scout troop. MS would and does [I sense] see such as bad form and simply wrong. The only thing more wrong was a person - the Honorable Judge Jackson - a neophyte with a degree in history.
|