Unpatched IE bug exploited in targeted attacks
'More than a few organizations' hit
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
Unknown attackers have been targeting a previously unknown vulnerability in Internet Explorer to take control of machines running the Microsoft browser, security watchers warned on Wednesday.
The exploits were hosted on a page of an unidentified website that had been breached without the owner's knowledge, according to antivirus provider Symantec, which discovered the attacks a few days ago. The perpetrators then sent emails that lured a select group of people in targeted organizations to the booby-trapped page, causing those who used IE versions 6 and 7 to be infected with a backdoor trojan.
The exploit required no interaction on the part of victims and gave no indication what was happening. While the exploit page was found on a single website, Symantec researchers warned the attacks may have been widespread.
“Looking at the log files from this exploited server we know that the malware author had targeted more than a few organizations,” they wrote. “The files on this server had been accessed by people in lots of organizations in multiple industries across the globe.”
In an encouraging sign, few of the visitors were affected because they weren't using a vulnerable browser, they added.
Version 8 of IE may also be vulnerable, but a security protection known as DEP, or data execution prevention – which is turned on by default – causes the browser to crash rather than to remotely execute the malicious code, Microsoft said. DEP, which was first added to IE 7, is designed to lessen the damage of such attacks by preventing data loaded into memory from being executed. While hackers have figured out ways to bypass the technology, so-called heap-spraying attacks don't work well with this particular bug.
The security flaw resides in a part of IE that handles CSS, or Cascading Style Sheets, tags. As a result, the browser under-allocates memory, allowing data to be overwritten in memory vtable pointers. By spraying memory with special data, an attacker can cause IE to execute code.
The report is the latest reminder of the benefits of moving to the latest version of IE – or to a different browser altogether. Those who must use IE versions 6 or 7, should consider augmenting it with EMET, Microsoft's tool for locking down older applications. It can be used to add DEP and other security mitigations to a variety of programs, including IE and Adobe Reader.
Microsoft didn't say when it planned to patch the vulnerability, but Jerry Bryant, a spokesman for Microsoft response, indicated the bug probably didn't warrant a release outside of the company's normal update cycle. That means the earliest we're likely to see a fix is December 14.
COMMENTS
Elsewhere, over the rainbow...
"The problem lies elsewhere than in Microsofts hands alone."
Um, yes, we could shut down the Internet for a month. Or nuke a couple continents, is that why you wanted to know which website was serving malware?
"Can I ask, one more time, when will you see the situation for what it really is.?"
There is the phrase "face-palm". Is there a phrase "face-mirror"?
The bug is in Microsoft code. The fix will be in Microsoft code. Nothing practical that anyone else does will change that. (well, except avoiding Microsoft code).
Are you somehow suggesting that everything else bad/wicked/malevolent/stupid out there in the world *must* be fixed, first, as that is the *real* problem, rather than blaming Microsoft for yet another bug that should have been caught by their much vaunted internal code reviews that they reassured the world would make them "much better now"?
Sancho, did the Don get away from you again? Can you keep him away from the keyboard at least?
Maybe Microsoft...
Maybe, yes, Microsoft are not the only ones to blame here for the fault; while there is the small matter of those who find such faults and abuse them, it is quite important to note that this is a vulnerability being exploited right now and no fix is apparently forthcoming for 6 weeks.
Yes, other platforms have issues, other platforms do get them but rarely are they going to just sit and wait for 6 weeks to release a patch when they are actively being abused.
If only
the damned browser was'nt tied into the OS so closely, the attack sequence would go like this
<website> download dodgy code
<browser> hey lets execute code and change core system files to run the malware
<OS> like f**k you will, block and crash browser
Instead of the m$ way of
<website> download dodgy code
<browser> hey lets execute code and change core system files to run the malware
<OS> sure go ahead. opps you seem to have hosed all my dll files, and sent every password/cookie off to a Russian server Oh dear I've crashed
Boris
<<still sulking after a poxy VBscript that loaded a worm trashed his WinXp box

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider