Microsoft preps fix for IE 8 flaw that makes safe sites unsafe
Third time's the charm
Microsoft will release an update intended to rid Internet Explorer 8 of a vulnerability that can enable serious security attacks against websites that are otherwise safe.
The change, which will be introduced in June, will be the third time in six months that Microsoft has tweaked a feature used to filter out XSS, or cross-site scripting filter, attacks against websites. The filter, which Microsoft introduced with the release of IE 8, is designed to strip out malicious commands that exploit the vulnerabilities, which plague many websites.
As The Register reported in November, the new XSS filter could be exploited to introduce XSS attacks on sites that otherwise weren't vulnerable. Microsoft has twice made changes to the feature, once in January and again in March, but last week, researchers at the Black Hat Security Conference in Barcelona showed the filter still injected threats into sites that included Google, Wikipedia, Twitter and even Microsoft's own Bing.
"This issue manifests when malicious script can 'break out' from within a construct that is already within an existing script block," David Ross, of Microsoft Security Response Center, said here. "While the issue identified and addressed in MS10-002 was identified to exist on high-profile websites, thus far real-world examples of the SCRIPT tag neutering attack scenario have been hard to come by."
XSS exploits allow attackers to inject malicious code or content into trusted websites by convincing victims to click on booby-trapped links. Because the links contain the well-known domain names, they rarely arouse suspicion, as was the case recently when admins from the Apache Foundation visited tainted links that exposed their login credentials and led to a serious security lapse.
Features like Microsoft's XSS filter, or a similar protection offered in the NoScript add-on for Mozilla Firefox, are designed to prevent such attacks. ®
@ Neal 5
Have a look at this > http://noscript.net/features#xss
In other news...
"the third time in six months that Microsoft has tweaked a feature used to filter out XSS, or cross-site scripting filter, attacks against websites."
Oh noes! This is their third attempt - have they got it right this time?
Is there *any* MS software that doesn't have a security risk? What about "calculator" and "solitaire"?
The real reason for this and similar foul-ups from all vendors is the appallingly low level of expertise among developers/programmers. Sure they can _code_ but they clearly can't see the functional implications of the code they create.
Until software development becomes a genuine engineering discipline performed according to sound core principles by attentive, thoughtful and competent people, things will never change for the better, and we'll go on having to apply streams of patches. Would you fly in a plane that required "patching" every few days? Not bloody likely! So why do we tolerate it in software? Probably only because the vendors already have us by the balls, so we hand them our hearts and minds.