Ramblings of an old Doc

 

All versions of IE (IE6-IE11) are vulnerable to a remote code execution which works through a memory corruption bug. Attacks have been reported, so this isn’t a ‘theoretical’ thing. The reported attacks are using attacks on IE8 and IE9. The source for this is http://technet.microsoft.com/en-us/security/advisory/2887505 :

“Mitigating Factors:

  • By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability.
  • By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML email messages in the Restricted sites zone. The Restricted sites zone, which disables script and ActiveX controls, helps reduce the risk of an attacker being able to use this vulnerability to execute malicious code. If a user clicks a link in an email message, the user could still be vulnerable to exploitation of this vulnerability through the web-based attack scenario.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a web-based attack scenario, an attacker could host a website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.”

So, if you’re running IE on Windows Server 2003, 2008 R2, 2012 and 2012 R2 the vulnerability is mitigated.

There are work arounds and they are on the security advisory link above under “Suggested Actions”.

Another ‘work around’ is using FF or Chrome until a real fix comes along. MS is still debating about a patch for it.


Comments
on Sep 18, 2013

Another ‘work around’ is using F or Chrome until a real fix comes along.

Sounds more like a permanent 'work around' to me........

on Sep 18, 2013

One more reason to give IE the boot. IMO

on Sep 18, 2013

Well like you would expect and hope, Microsoft has released a fix for this.   It hasn't though shown up in updates yet for me. 

http://www.nbcnews.com/technology/microsoft-rushes-out-fix-prevent-internet-explorer-attacks-4B11188131

EDIT:  Damn, and I just updated to IE 10 this morning too, go figure.  

on Sep 18, 2013

Philly, the nbcnews article is about the fixes I referred to in the OP .

 

on Sep 26, 2013

the fixit only works for 32 bit ie. and it won't show up in the autoupdate either, like all the other fixits.

the problem isn't so much whether you use alternative browser rather than ie, but that some programs just likes to call IE instead of your default browser. (some old .net thing i think)

 

i've got emet 4 from a while back. not sure if it's properly configured or not.. but at least it's pre-configured for ie. which is one of the workarounds mentioned.

on Sep 26, 2013

How in the hell do the people that write the codes for IE keep their jobs?!? Or do they have one hell of a revolving door there?

on Sep 26, 2013

I think all browsers are vulnerable, Po. The hackers just go after IE more because of its market share.

 

on Sep 26, 2013

Snowman
Sounds more like a permanent 'work around' to me........

But it works for me!