Slashdot Mirror


IE 0-Day Flaw Used In Chinese Attack

bheer writes "A zero-day attack on IE was used to carry out the cyber attack on Google and others that's been getting so much ink recently, reports The Register, quoting McAfee's CTO. While the web (and security) community has pointed out the problems with IE's many security flaws (and its sluggish update cycle) in the past, IE shows no sign of vanishing from the corporate landscape."

24 of 318 comments (clear)

  1. A major security flaw in IE? by XPeter · · Score: 5, Funny

    This is unheard of!

    --
    "The difference between genius and stupidity is that genius has it's limits" - Albert Einstein
    1. Re:A major security flaw in IE? by Monkeedude1212 · · Score: 4, Funny

      No no no, you aren't seeing it.

      Google can stay in China, or pull out, or do whatever its nefarious plan is, and now they can BLAME MICROSOFT!

      Don't you know what this means?!?!?!?!?!?

      Clearly this is all an elaborate ruse to market Chrome!

    2. Re:A major security flaw in IE? by Knara · · Score: 5, Funny

      Google can stay in China, or pull out,

      It's far too late for Google to pull out of China. It should have known that the pulling-out method is not a reliable form of birth control, and now it needs to take responsibility for it and China's love child, Baidu.

    3. Re:A major security flaw in IE? by CodeBuster · · Score: 5, Funny

      This is unheard of!

      Until it gets reported or exploited, then everyone knows about it.

    4. Re:A major security flaw in IE? by spinkham · · Score: 4, Insightful

      Oh really? Tracing JIT JavaScript interpreters are trivial? Parsing PNG, GIF, JPEG, SVG, and even more image formats is trivial? The rules for the same origin policy including inheritance to iframes and the like, cross domain access, content encoding, proxies, plugins, memory management, not to mention multiple tabs with concurrent access to all these things.. All these are all trivial to you? Man, I'd use your browser in a second, because no one else can manage the complexity. The standards are nice as far as they go, but not complete and there's lots of legacy crap out there. HTML 5 does codify better parsing behavior and other thigns that have been missing for the standard, but still doesn't cover everything.

      For a very quick overview that just grazes the surface on how hard this stuff is, see the Browser Security Handbook by Michal Zalewski.

      Firefox lists 35 security flaws in Firefox 3.5 alone, and that's only been out since June.

      Yes, ActiveX is/was/will be a bad idea, but at least it requires a click through now, and runs with DEP in IE 8. Plugins have the same problems on native code for Firefox and the other browsers too, now that Firefox has market share starting to see a rise in plugins and security flaws there instead.

      Now, I'm not a Windows or IE fanboy, actually I hate the darn thing and run Firefox most of the time. But I do break web software for a living, and know how complex this stuff is and how nobody has it right. Both IE and Chrome have added some interesting security features lately to help contain flaws when they do occur, but nobody has yet written perfect software and there will continue to be security flaws in all browsers.

      --
      Blessed are the pessimists, for they have made backups.
    5. Re:A major security flaw in IE? by rtb61 · · Score: 4, Informative

      http://news.cnet.com/China-looks-into-Windows-code/2100-1016_3-5083458.html. The microtrolls are bad enough of the mods but leave the out and out lies alone it looks silly.

      --
      Chaos - everything, everywhere, everywhen
    6. Re:A major security flaw in IE? by spinkham · · Score: 4, Insightful

      The format is trivial, but oddly enough a secure parser is not.

      One of the exploitable Firefox bugs this year is in the GIF parsing code, in a situation where there are multiple images in a GIF file, and one has a small color map and is malformed in a specific way, followed by one with a larger color map.

      See https://bugzilla.mozilla.org/show_bug.cgi?id=511689 for more details.

      Java and windows have also had GIF parsing security bugs in the past:
      http://sunsolve.sun.com/search/document.do?assetkey=1-26-102760-1
      http://www.checkpoint.com/defense/advisories/public/2008/cpai-02-Sepa.html

      Remember, this GIF parsing is but one of the things I mentioned, and I only mentioned a small faction of the potential bugs in any web browser.

      This is why security is hard: Secure software is perfect software, and we don't write perfect software.

      --
      Blessed are the pessimists, for they have made backups.
    7. Re:A major security flaw in IE? by spinkham · · Score: 4, Interesting

      Honestly, if you think you can just slap a few open piece of software togeather and have a secure functioning browser, you're smoking something. There's a reason there's only 4 browser engines, and that's because it's *hard*.

      Firefox is NOT doing well at producing a secure browser. They patch faster the IE, but every Mozilla 3.5 release has between 2 and 6 critical(read likely exploitable) security flaws. They have had 35 flaws total in the last 7 months. http://www.mozilla.org/security/known-vulnerabilities/firefox35.html

      Chrome is doing somewhat better, but they have only 2% market share, and not as many people hunting for bugs. Still a number of critical bugs fixed last year.

      Just ran sloccount on firefox 3.5.7 source tree, and it says there are 2.7 million lines of code. For comparison, the Linux 2.6.32.3 has 8 million lines, so Firefox is only 1/3 the size of the full Linux kernel, including all drivers.
      The average code has about .5-1 security bugs per 1k lines of code. That means we can expect 1350-2700 security bugs in Firefox.

      Just so this isn't all about Firefox, Chromium (the open source branch of Chrome) largely reuses software as much as possible, and has 4.5 million lines of code. That's a huge project. They seem to have less custom parsers, but upstream bugs still do affect them.

      The point of this isn't to say that Firefox or Chromium is worse then IE, it's just that modern web browsers are *complicated*. Security is hard even for small projects, and 2.7-4.5 million lines of code is not small. You can hate on IE all you want for web standards support (SVG and XHTML are two nice places to start), but they're actually not doing much worse then the other players for security at the moment. Yes, IE 6 is a piece of crap, and if you're still running that then you deserve what you get, but IE 8 is decent.

      --
      Blessed are the pessimists, for they have made backups.
  2. More than just IE by FalleStar · · Score: 5, Informative

    If you bother to RTFA (I must be new here, right?) you'll see that it wasn't JUST an IE zero-day that was used in the attack.

    "While we have identified the Internet Explorer vulnerability as one of the vectors of attack in this incident, many of these targeted attacks often involve a cocktail of zero-day vulnerabilities combined with sophisticated social engineering scenarios." - George Kurtz

    So IE is partially to blame, but you can't just say that this is MS's fault.

    1. Re:More than just IE by calmofthestorm · · Score: 4, Insightful

      Even if it were 100% microsoft, zero-days happen. The only problem is that with MS, they're 31 days, not zero days.

      --
      93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
    2. Re:More than just IE by dclozier · · Score: 5, Funny

      So IE is partially to blame, but you can't just say that this is MS's fault.

      You really are new here. Of course it was all Microsoft's fault. ;)

  3. It's not stupidity by liquiddark · · Score: 5, Insightful

    Corporate users largely work on intranets, and intranets are largely supported by guys who don't have the resources a professional development team has. So corporations buy large make-your-own-adventure web-ish packages like Sharepoint, and suddenly they're locked into IE for another cycle, and the whole ugly repeats itself. It's genuinely difficult to not get locked into somebody's product stack, and Microsoft's is, on the whole, no worse than anybody else's.

    1. Re:It's not stupidity by liquiddark · · Score: 4, Insightful

      You might think that, but try supporting a massive suite of web applications that all have their own browser ticks, all of which were critical for something just shy of a minute, but which are maintained because retiring one would cause one guy (who always, somehow, happens to have the necessary clout) to die of unproductivity. Until you've lived in that situation for years on end it is wise to withhold judgement.

    2. Re:It's not stupidity by yuna49 · · Score: 5, Informative

      According to TFA, this vulnerability was in IE6.

      No, only IE 5.01 SP4 and IE 8 are not vulnerable without enabling "data execution prevention." The attackers apparently targeted IE 6, but nearly all other versions can be compromised.

      From TFA:

      "A security feature known as data execution prevention, which prevents data loaded into memory from being executed, will block the particular exploits McAfee has observed. But Kurtz warned the vulnerability exists in all versions of IE except for IE 5.01, service pack 4, and that it would be possible for attackers to work around the protection.

      In an advisory, Microsoft recommended people use DEP, which by default is enabled in IE 8 but must be turned on in prior versions. The statement also advised users on Vista and later versions of Windows to run IE in protected mode. The advisory didn't say when an update would be released that patches the vulnerability."

    3. Re:It's not stupidity by Carnildo · · Score: 4, Insightful

      Given the opportunity, I'd make everyone ignore a half dozen warnings.

      Fixed that for you. Warning overload is one of the biggest problems facing computer security today. Since so many of the warnings the average user is bombarded with are meaningless, the genuine threats get lost in the noise and are ignored.

      See also: The boy who cried "wolf".

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  4. Not IE, Adobe's PDF Reader 0 day Flaw by Eyah....TIMMY · · Score: 5, Informative

    From an earlier /. article: http://arstechnica.com/security/news/2010/01/researchers-identify-command-servers-behind-google-attack.ars

    From the article in this post: The previously unknown flaw in the IE browser was probably just one of the vectors used in the attacks .
    I love the "probably"

    --

    It is not enough to have a good mind. The main thing is to use it well. - Rene Descartes (1637)
  5. Chinese govt inspection of MSFT code? by SillyValley · · Score: 5, Interesting

    I recall MSFT allowed the Chinese government to look at Windows source code a few years back. I wonder if the vulnerable IE6/7/8 code was part of the code provided to the Chinese government, but IE5.4 (not vulnerable to the latest attack, apparently) didn't include the problem code? This is something that can be checked. It could be an indication of whether the Chinese used the source code inspection as a road map to identify vulnerabilities for attacks like these.

    1. Re:Chinese govt inspection of MSFT code? by cbhacking · · Score: 4, Interesting

      It is worth noting that unless you specifically exclude IE8 from DEP (or disable DEP globally) then it is not vulnerable to this attack. You can also enable DEP (either via opt-in or by switching the default behavior system-wide to opt-out) for the previous IE versions.

      Nonetheless, it's possible that the vulnerability was discovered in the manner you suggest. I'm not sure they saw the IE8 code, but if the same vulnerability is used on all versions it's probably in code that hasn't changed in a while.

      --
      There's no place I could be, since I've found Serenity...
  6. Re:You know what this means by Anachragnome · · Score: 4, Interesting

    That is pure genius.

    There are Sooooo many people that don't know how to find anything on the web without using Google that if Google did stop supporting IE, many of those people would start using Firefox simply to use Google. And that would be a huge foot-in-the-groin for Microsoft, even if it doesn't DIRECTLY benefit Google.

    Methinks it would avoid any anti-trust issues as well.

    Considering the topic of this thread, it might actually help to prevent further Chinese highjinks.

  7. No real fix... by Aoet_325 · · Score: 5, Interesting

    Sadly, microsoft doesn't seem to have anything you can do to fix this.
    http://www.microsoft.com/technet/security/advisory/979352.mspx
    It's seems all they advise will only reduce your odds of getting hit (by helping protect against the methods they've seen used to exploit it) and reducing the damage done after IE runs the malicious code on your system.

    What they should be suggesting is that people not use IE on the internet (if possible) until this is fixed.

    '0 day' exploits are everywhere. What matters to me is that once discovered they are quickly patched or at the very least, a work around that actually prevents exploitation is provided.

    I'd be interested to know more about the social engineering aspect of this attack. Was this more of the usual attempts (something that really should have been caught by anyone who knows better than to open random attachments and click links from strangers) or was there something much more involved that allowed the attackers to gain sufficient trust that any one of us would have likely fallen for this. Did the attackers spend months building a strong level of trust with the people at these companies or did someone click an on E-card?

  8. Re:Not PDFs? by biryokumaru · · Score: 5, Insightful

    I know, why isn't the solution ever "Use an alternative PDF viewer?" Instead of "Update Adobe Acrobat to another version filled with gaping security flaws."

    --
    When you're afraid to download music illegally in your own home, then the terrorists have won!
  9. Re:?Senior? by Runaway1956 · · Score: 5, Insightful

    And, "some of us" find these posts amusing. The FACT is, Microsoft products are the primary vector for every malware known to man.

    Using your logic, we should go back to dumping sewerage in the streets. I mean, yeah, it's kinda nasty, but plenty of people lived to be old aged in medieval Europe, right? They were probably the people who didn't click on purple apes too. Just forget about that plague thing. Over-hyped nonsense.

    --
    "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
  10. Oh, but it doesn't count, right? by gillbates · · Score: 5, Informative

    Because according to Microsoft, system vulnerability is determined by the following formula:

    Vulnerability = (time of patch - time of discovery) * number of exploits.

    Clearly, since the vulnerability was never publicly discovered, no patch was needed, right? Clearly, since the exploit was never published, it was not a security risk, right?

    For years, those outside the FOSS community behaved as if an unknown or undiscovered (or rather, unpublished) exploit was not a security vulnerability for the purposes of calculating risk. Rather, we were led to believe, by MS and others, that only unpatched systems were vulnerable. For years, I watched as countless IT folks repeated the mantra that a fully patched MS system was just as secure as any other.

    It always seemed obvious to me, but apparently not to others, that risk should be calculated using not on the time of discovery and publication, but rather, upon the ship date of the software. (i.e., a vulnerability discovered 3 years after ship date, but patched a month after discovery means your system was vulnerable for 39 months, instead of only one as the MS method calculated vulnerability.

    I think Google is big enough that people will now recognize that system security is not just a matter of patch early, patch often, but also a characteristic of the entity behind the code. Despite what Microsoft marketing would have you believe, the company can't produce a secure OS because they understand neither the problem, nor even the question.

    The reason Linux is more secure than Windows is due not merely to the fact that it is open source, but also because those who work with UNIX understand the problem of system security. It doesn't mean Linux is perfect, only that it fares much better from a total-risk perspective. Microsoft never really grasped that security was a fundamental system design consideration, rather than a problem to be patched on the back-end of SW development. While they have *tried* to address the security issues (and have been somewhat successful, but only due to their brute-force efforts), they still have a product-design mentality which places ship dates above system quality, and usability above overall security. The fact that they still consider anti-virus software and constant patching a normal part of computing indicates they've failed to grasp the lessons learned of the past 3 decades.

    For Microsoft, security is a checkbox feature, not a way of doing business. Maybe, now that Google was compromised by a type of exploit Microsoft, et al, considered of minimal, if not zero, risk, the world will change its opinion of the acceptability of software requiring constant patches and add-on kludges (i.e. anti-virus sw) just to function normally.

    --
    The society for a thought-free internet welcomes you.
  11. Confused by Microsoft P.R.? by Futurepower(R) · · Score: 5, Insightful

    You said, "Using IE6 is like using Firefox 1. Are you feeling lucky?"

    Note that you were confused by Microsoft public relations that is apparently trying to avoid responsibility. Here is a quote from the article:

    "Our investigation has shown that Internet explorer is vulnerable on all of Microsoft's most recent operating system releases, including Windows 7."

    Windows 7 uses Internet Explorer 8, the latest version. According to Microsoft, all versions of IE are vulnerable. But Microsoft makes a statement that is apparently meant to confuse:

    'Shortly after the report, Microsoft confirmed the new IE vulnerability was "one of the vectors used in targeted and sophisticated attacks against Google and possibly other corporate networks." A company statement said the attacks were carried out against version 6 of the widely used browser and suggested users protect themselves by enabling security features that have been added to successor versions'

    At present, 2010-01-15, 03:59 PDT, the Microsoft Security Advisory (979352) tells the truth, but also in a way apparently designed to confuse. This is an exact quote, after the confusing introduction, eliminating other confusing words:

    "... Internet Explorer 7 and Internet Explorer 8 on ... Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 are affected."

    At present, here is the full, confusing paragraph from that Microsoft web page:

    "Our investigation so far has shown that Internet Explorer 5.01 Service Pack 4 on Microsoft Windows 2000 Service Pack 4 is not affected, and that Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4, and Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 on supported editions of Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 are affected."

    For the apparent reason Microsoft allows IE to be insecure, see the New York Times article Corrupted PC's Find New Home in the Dumpster. As the article explains, operating system corruption and vulnerability to malware is very profitable for Microsoft and its main customers, who are computer manufacturers.