Slashdot Mirror


New IE Holes Discovered

joelt49 writes "Yahoo! News is reporting that 7 new security holes for Internet Explorer have been discovered by a Chinese researcher; however, there apparantly aren't any attacks on IE yet." The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list. Sure, a lot of people don't like Microsoft, but that's no reason to make it worse for the millions of people who are forced to use Microsoft products, especially for security holes which have yet to be exploited.

38 of 801 comments (clear)

  1. Incident response times by Tet · · Score: 5, Insightful
    The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list.

    Yep, not ideal. But it'll be interesting to see whether MS's claims of having a faster response time to security incidents that the Linux community stands up. Will they have a patch available withing the next day or so? You can guarantee that the Mozilla or Konqueror communities would have in the same circumstances...

    --
    "The invisible and the non-existent look very much alike." -- Delos B. McKown
    1. Re:Incident response times by Anonymous Coward · · Score: 3, Insightful

      You can guarantee that the Mozilla or Konqueror communities would have in the same circumstances...

      And would the Mozilla and Konqueror communities fully regression test their changes against all of the various software it might affect.. no.

    2. Re:Incident response times by Chexsum · · Score: 5, Insightful

      Itd be really strange if Mozilla broke my Window Manager or something. What exactly would they need to test it with?

      I can understand Internet Explorer needing to be tested against the rest of Windows and its APIs but Mozilla is a stand-alone web browser - as long as the API isnt affected it ['full regression testing'] shouldnt matter too much IMO.

      --
      Pixels keep you awake!
    3. Re:Incident response times by Avihson · · Score: 5, Insightful

      Microsoft has been using the paying community as QA since at least MS-DOS 4.0 Have you been living in a cave all these years?

      The whole premise behind FSF is that it is FREE, the user accepts some responsibility in the transaction, in this case by reporting bugs and helping to test beta versions before the code is released live. You seem to be saying that Microsoft has never released code that was not finished, 100% Quality Assured, no Security holes.....

      If you believe so strongly in your statements, why do you post AC?
      So I say Mod the Grandparent DOWN, MS whiners be damned!

    4. Re:Incident response times by curious.corn · · Score: 4, Insightful

      Oh, the joys of forceful integration... ;-) Now do you understand the importance of clean independent components with defined and carefully thought out APIs?

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
    5. Re:Incident response times by Anonymous Coward · · Score: 3, Insightful

      If you wanted a fix in a version of Apache, they'd tell you to upgrade.

      But I have to upgrade a minor version (!) for free (!). I don't have to upgrade to apache-2. Even if I had to do this, I won't have to pay money to the apache foundation - so they have no interest in making me upgrade to a higher major version. That's a big difference in my opinion.

    6. Re:Incident response times by Error27 · · Score: 5, Insightful

      Please list one problem someone has had because of a Mozilla security fix.

    7. Re:Incident response times by arkanes · · Score: 5, Insightful

      Doesn't matter - MS claims a 24 hour response time. Lets see it happen.

    8. Re:Incident response times by NortWind · · Score: 4, Insightful

      Microsoft has released service packs that kill peoples applications, so much so that they have had to remove the service pack and put in a differnt one to patch the broken patch. Even Microsoft can't check the way everything works with everything.

      The big differnce is that with open software, you can patch it yourself, or hire somebody to patch it for you. With MS, you can't patch it, and unless it effects enough people, you can't get MS to patch it either.

    9. Re:Incident response times by Minna+Kirai · · Score: 4, Insightful

      A critical bug in Konqueror and all of KDE becomes useless.

      This gets back to the terms sproketboy used: no "commingling" in a "properly written application".

      I won't go into a 10-page lecture on software engineering. But just because an application is depended on by any others doesn't mean they're comingled, or improperly written. A good component app will have a limited number of interfaces to the rest of the system (on the order of 10-200, and hopefully towards the low side).

      Testing the program's correctness on those interfaces gives you a high trust that it'll work correctly in the larger system.

      Microsoft(tm) IE(r) isn't like that. It doesn't have defined interfaces to the rest of the system. Its not an application which runs on the OS kernel and talks with other apps. It's source code is intermixed with much of the rest of the Windows OS. Testing every interface isn't enough to show that a new version is working right... you'd have to go through every line of code and see how it might possibly perturb Windows itself.

      Compared to component-interface testing, that's a prohitably lengthy task; a combinatorical explosion of places to check.

      no Kate working no editors

      Again, Kate is one component, and testing that component's agreement with each of its public interfaces should be enough to verify there are no critical bugs. That only works if the components are well-separated enough. But separation leads to slowness, and Microsoft wants to be fast.

    10. Re:Incident response times by Locutus · · Score: 4, Insightful

      Mod the parent up. This one hits the nail on the head and is the heart of what's wrong with MS Windows and right with Linux. What Microsoft claims as integration is done in a way which brings the whole house down when one small part fails. The co-mingling of applications with the OS. Legal documentation even showed that this was originally done for anti-competitive reasons and now is being presented as the latest half-baked why MS Windows is supposedly better than Linux. This is not the design methodology used in the *nix world.

      This is also something to watch out for when developers try to mimic the Microsoft Windows system while making Linux more and more user friendly.

      IMHO

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    11. Re:Incident response times by mentin · · Score: 4, Insightful
      This is not the design methodology used in the *nix world.

      Code reuse is code reuse, whether it is Windows, Unix, or any other OS/app. Modern programmers are taught to do code reuse, and saing "This is not the design methodology used in the *nix world" is plain stupid.

      When gzip security hole was discovered, it hit hundreds of Unix applications, because they reused the code from this library. Is the "design methodology" any different?

      The gzip bug demonstrated that it sometimes can even be worse on *nix, due to source code coping instead of shared libs, so that the bug had to be fixed in multiple places.

      By the way, Netscape was / Mozilla is actively trying to make itself a platform for writing applications using its XPCOM/XUL and other technologies. It is not very successful so far, but when it will, its bugs and patches will hit lots of independent applications, just like bugs/patches in IE do now.

      --
      MSDOS: 20+ years without remote hole in the default install
  2. it wouldn't change anything by __aaitqo8496 · · Score: 5, Insightful

    I don't blame this guy for not going to Microsoft first. Given thier track record, more than likely, they would have ignored him until someone publicly announced the problems.

    P.S. Is it news anymore that IE has holes?

    1. Re:it wouldn't change anything by muffen · · Score: 5, Insightful

      Given thier track record, more than likely, they would have ignored him until someone publicly announced the problems.

      You may be right, but it still doesn't change anything. I think this guy should have told Microsoft first, waited, if they don't respond within 48 hours, report it.
      If you get a standard stupid automated copy/paste reply, report the holes.... but you SHOULD give the company some notice. As stated in the article, not giving the company any info just makes it bad for anyone having to use IE.

      Is it news anymore that IE has holes?

      Nope. Seriously, who here gives a crap about IE holes? Everyone here probably knows that using IE is about as secure as getting water in a fishingnet.

    2. Re:it wouldn't change anything by AtomicBomb · · Score: 5, Insightful

      It is pretty pathetic to deal with some big software company like Microsoft when reporting bugs... There is no simple way. A friend of mine did some scripting and discovered an obscured w2k bug (no big deal just causing yet another blue screen) by pure chance. He did some detective work and nailed down to the exact condition that triggers the problem. Since we are not doing security or serious low level programming, we don't have links with any relevant person in MS. When contacting the local MS office (we are in a small country, btw), the guy on the other end of the phone had no clue and put us thru technical support. Read: demanding $$$.

      At the end, we did not bother. After a few more months, it was made public (not by my friend though). Nowadays, reporting MS bug becomes a dangerous maneouver... If MS is really serious about security and good quality software, they would put a contact on the front page and offer reward for anyone who spots a new major bug. Before then, I don't see why we need to be nice to MS.... They say they are capitalist. We should respect their value and don't do any free work for them...

  3. It's hardly bad... by shfted! · · Score: 5, Insightful

    Sure, a lot of people don't like Microsoft, but that's no reason to make it worse for the millions of people who are forced to use Microsoft products, especially for security holes which have yet to be exploited.

    If OSS people can fix the bugs in less than half a day, it should be a piece of cake for a giant software company with lots of programmers to do the same. Sure, a days warning would have been nice, but if there isn't a fix by tonight, it only shows badly on Microsoft.

    --
    He who laughs last is stuck in a time dilation bubble.
    1. Re:It's hardly bad... by curious.corn · · Score: 4, Insightful

      Real programmers don't need to regression test the whole world for a simple bug: they fix the broken method, recompile and repackage. Real programmers design clean APIs and classes where the public methods don't need to change to fix a silly bug. On the other hand if the security fix requires breaking class compatibility then it's not a bug, it's a poor design failure...

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
  4. blablabla by Anonymous Coward · · Score: 5, Insightful

    The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list.

    Believe me, in these days that is the only way to report bugs AND making sure they'll get fixed.

    Dream world scenario:

    1) Report bug to company
    2) Company will announce the bug to the public
    3) Company will fix the bug as soon as possible

    Real World scenario 1:

    1) Report bug to company
    2) They don't report it to the public and they don't fix it
    3) You report it to the public
    4) Company sues you for IP violation or any other shit they can pull out of their asses

    Real World scenario 2:

    1) Report it to the public (anonymously).
    2) Company will fix it

  5. Immediate full disclosure is best security practic by Anonymous Coward · · Score: 5, Insightful

    Seriously - AS SOON AS THERE IS A VULNERABILITY, I, as a sysadmin, want to know about it. I don't give a flying fuck about Microsoft's reputation, or whether "vendors need time to patch the hole" - while there is a known hole, I DON'T WANT MY FUCKING SYSTEM ONLINE. If a nice guy can discover it, the bad guys probably already have.

    The "give us time to fix the hole/do a P.R. coverup" fiasco is WHY I DON'T USE MICROSOFT SOFTWARE ANYMORE.

  6. Public mailing list? by Amiga+Lover · · Score: 5, Insightful

    The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list.

    Thats because Microsoft's past record is to ignore people who have contacted them privately regarding security issues, or take legal action against them.

    If you really wanted something fixed by MS, and the last 15 times you'd contacted them they'd ignored you, but you've seen someone else release information into the wild and get MS's attention re: a fix within hours... WWYD?

  7. haha by SHEENmaster · · Score: 3, Insightful

    I can understand the desire for such vulnerabilities to be fixed before going public, but Microsoft has been known to sweep exploits under the rug for as many as twelve years. Exploits are a common fact of life with Microsoft products, and its better that this exploit was released to all as an explanation than as a virus/worm.

    --
    You can't judge a book by the way it wears its hair.
  8. At least he reported it to someone!!! by Seahawk91 · · Score: 3, Insightful

    WE could have found out about it when our sytems started acting up.

  9. Forced to use IE? by Realistic_Dragon · · Score: 4, Insightful

    This is not like Windows-Linux, where there is a steep learning curve.

    Mozilla (or Phoenix) is a slick alternative with an almost zero learning curve to pick up the same level as IE. It also takes almost no time to learn features _that aren't in IE anyway_ that help you see the internet in a much more useful way (ad blocking etc).

    No one is forced to use IE with very few exceptions:

    People who have it mandated at work, but that's work's problem not yours - they could change too.
    People on dialup who have a very slow net connection - but they probably have it on a dial up CD.
    People who use it's integrated rendering engine for OE/HTML email - but you can change that easily too.
    People who _must_ access IE only websites - but there are very few of these any more, and you can always use IE just for these to lower your exposure.
    Microsoft Zelots who refuse to believe that Free software can be any good - but they deserve everything they get.

    --
    Beep beep.
  10. Sometimes it's all about timing by harmonics · · Score: 5, Insightful

    While my firm is a strong supporter of full disclosure, this is rather over the top.

    What makes it worse is the timing, over a holiday weekend (States side), where most systems staff will be unable to apply patches or mitigate risks.

    Now this is an Internet Explorer exploit, hence, few people using IE at work over the weekend. It still provides 48 hours for a few unsavory individuals to develop exploits for Monday morning.

    We need to exercise better judgement when dealing with vendors and security issues, this isn't the first time things like this have happened, and won't be the last.

    Perhaps we should consider spending more effort creating a Security Researchers Organization as has been discussed on BugTraq .

    Until we have a strong unified organization I believe we will continue to see unresponsive vendors and poorly timed vulnerability releases.

  11. Re:I've been trying my best to switch people away by Chalybeous · · Score: 4, Insightful

    I use Mozilla Firebird, myself, and like you, I've tried to encourage my friends to switch.
    Doesn't help much when I'm forced to use a university workstation (like today), but I find it's a better quality browser than IE. Renders faster, blocks pop-ups, and I find tabbed browsing to be pretty much invaluable.
    Of course, the best thing about Firebird is, I can still watch Doctor Who: Scream of the Shalka ;-)

    There are, of course, some times when you have to use IE (like Windows Update, though I guess I could always just download each update manually).

    The big problem I've hit is that, even with all these MSIE vulnerabilities that come out on a near-weekly basis - not to mention annoying pop-ups and pop-unders, and other little security-related issues - I don't seem to have any success.
    So what's your persuasive technique for getting people onto pre-1.0, non-MS, reliable-but-not-100%-complete software?

    --

    "It is dark. You are likely to be eaten by a grue." -- Zork

  12. Re:Unbelievable Arrogance by thenextpresident · · Score: 4, Insightful

    "I'd like to know who the editor thinks are "forcing" people to use Microsoft products."

    People at work who have to use Windows because it's work mandated.

    Their's millions of those type of people...

    --
    Jason Lotito
  13. Re:Immediate full disclosure is best security prac by sqlrob · · Score: 4, Insightful

    it wouldn't have been 'a known hole', but to the Microsoft developers

    Prove it. Anything that can be found by a white/gray hat can be found or was already found by a black hat.

  14. Re:Forced? by MKalus · · Score: 5, Insightful

    I bet you most people in Big Corporations are forced to use windows (not that they know any different).

    I know I am forced to use windows at work, even though either a Mac or any Unix Desktop would do.

    I ditch IE whenever I can, but for example our HR Website and anything else RELIES on Windows, no way around it.

    --
    If you want to e-mail me, use my PGP Key.
  15. Re:Addendum by bug-eyed+monster · · Score: 4, Insightful

    Not very realistic unfortunately, when companies have invested so much in integrating (and accepting) some of the flawed functionality in IE.

    Are you talking about internet companies or companies using IE for their intranet apps? If a company is using IE-specific functionality to offer services over the internet, they deserve to get bitten periodically. I have no sympathy for any company that provides a service to the "public" but forces them to use one specific browser.

    On the other hand, it is quite common to use IE-specific functionality for intranet applications. That's not a problem, one assumes that the intranet server is safe. The solution is to continue to use IE for intranet (and remove all links to internet sites from intranet apps), but use a more secure product to access the internet.

  16. "Forced to use Microsoft products" ? by chrysalis · · Score: 4, Insightful

    I don't understand the "forced to use Microsoft products" part.

    Even when you need to work on Windows, why should you be _forced_ to use Internet Exploder?
    Mozilla is the first thing I always install on Windows.

    There are organizations where people are indeed forced to use a fixed set of software. In this case, if there's a security hole, the responsability belongs to the sysadmin who forced people to use broken and out of date software.

    --
    {{.sig}}
  17. Re:What I don't understand... by SoTuA · · Score: 3, Insightful
    Just imagine how many lives would have been saved if people had been fully aware of the incompetent design of the Explorer and bought other cars instead.

    Truly. Makes one wonder if there are internal memos in M$ that warn of the possible mayhem in IE and are swept under the rug like the Explorer chassis problems in Ford motor...

    Oh, and for bonus points, both products are "Explorers" ;)

  18. Its all about netrep by werdna · · Score: 4, Insightful

    The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list.

    Truth. But here's the problem. Microsoft's reputation for responsiveness (that is, not!) and collegiality (that is, not!) in these situations is awful. Nor does Microsoft treat those who report such problems with any degree of warmth. Having established its Chinese wall as it has, Microsoft has lost its standing to whine about non-collegiality of the world it has created.

    This is the entire point about open systems, or at least openness about security -- it leverages what happens out there. Frankly, I feel more secure knowing what are the leaks, whether they are addressed or not, than I do knowing there are secret leaks out there for someone to exploit without my knowledge.

    If Microsoft had a reputation: (i) for assuring that a report of a leak would be responsibly handled and escalated promptly and without agonizing pain on the part of the reporter -- who is doing Microsoft a favor; and (ii) for responsibly, promptly and professionally addressing the problem, I would feel much more sympathetic.

    The problem is that they don't. Maybe they will change as they said they would. But until they do, I'd rather hear the news in time to know for what I have to watch out than to have it buried while others who have discovered the leak exploit it.

    Here's the thing, it is highly unlikely that any leak that is discovered by me was discovered only by me. Others, less responsible than I, will disover a leak, find the exploit, and either keep it in their "bag of tricks," trade it or what have you. In any case, if I find it, the exploit is likely out there in someone else's hands. I'd rather know the problem than wait for the solution.

    Yes, the kiddies are more likely to play if it is readily "out there." But guys, that happens anyway, one way or the other. Beside, Microsoft seems far more responsive to public leaks than private ones -- maybe this kind of report is more likely to assure that the bug will be repaired than otherwise.

    And you spend much less time on hold . . .

  19. Re:No Exploit, eh? by djdavetrouble · · Score: 5, Insightful

    Truly. Also, if there is exploit code, someone is using it, just maybe not as part of a trojan or virus yet. Patch or no patch, you can bet that there will be an exploit being used in the wild within a matter of hours or a day at the maximum. The latest trojan/worm/virii are programs that deliver huge amounts of machines to spammers and hackers to become part of their DOS botnets or spamnets, with built in backdoors, etc. Were you on irc the day that the mirc xdcc flaw was discovered? I received no less than 30 malformed xdcc requests that day. Discovery of a new flaw is like free candy to script kidz. Twice the 0wned machines, half the hacking.

    --
    music lover since 1969
  20. What gets to me by remmy1978 · · Score: 4, Insightful

    The part about this story that gets to me is that the researcher didn't alert Microsoft before posting to a public mailing list.

    The part about this story that gets to me is that a single person finds 7 (!) holes/exploits by himself. Makes one wonder just how many things are left open simply because no one has looked at them yet. Scary.

  21. To be fair by fudgefactor7 · · Score: 3, Insightful
    I think we need a uniformly accepted timeline for public announcement of exploits. I envision something like this:
    (1) Upon discovery a possible exploit should be verified by at least one other researcher;
    (2) The exploit, once verified, is reported to the appropriate vendor (in this case MS);
    (3) The vendor has 7 business days to reply to the original notice, indicating receipt of the vulnerability and the status of the vulnerability (if any). Failure to reply indicates that the vendor thinks the vulnerability isn't a problem and it is assumed ignored;
    (4) After the reply is generated the vendor is given 21 business days to produce an interim patch. If no reply is generated by the vendor the vulnerability may be publically published 3 days later.;
    (5) If no patch is available 21 days later after reply is generated the vulnerability may be publically published immediately.
    Now if only people used something like that instead of going for the throat and trying to be "leet" and cool--some of this is just ego-pumping: Hey man, look at me, I found a flaw in MS' stuff! I'm so kewl...
  22. Running Down The Veulnerabilities by RzUpAnmsCwrds · · Score: 3, Insightful

    "Invalid ContentType may disclose cache directory"
    My Classification: Minor
    This isn't all that serious. The major threat is that a hacker could get your cache directory. The downloaded web page runs as part of the "internet" zone, meaning that there is no privelage elevation (IE has a zone system to give different pages different privelages).

    "LocalZoneInCache"
    Moderate/Severe
    This is more serious. It allows an attacker to modify files on the system or worse. Note that this *is not* the same as a root exploit, but it could be as damaging as running an executable. Note that the user *does* have to choose "open" in the download dialog, but they are not warned about the security risks and may not consider them as the file extention is ".htm".

    "MHTML Redirection Leads to Downloading EXE and Executing - Remote Compromise(requiring MYCOMPUTER zone)"
    Moderate
    This is somewhat less severe. It allows an attacker to download and execute an executable, but only if the user has already downloaded the page, saved it to disk, and executed it. The user might assume (incorrectly) that the file is safe.

    "MHTML Redirection leads to local file parsing in INTERNET zone"
    Severe (If an issue)
    I was not able to reproduce results with this veulnerability (IE6 SP1). Please comment if you can reproduce it. If it is indeed true, it would allow an attacker to parse the contents of a local file. They would need the absolute path. This could be used to discover potentially private information.

    "HijackClickV2 - Adding a Link to Favoriate List(requiring clicking a link)"
    Minor
    This would allow an attacker to add their site to favorites. The user would have to click a link and would have to release their mouse button over the favorites list (which is placed under their cursor after clicking the link).

    "execdror6"
    Severe (if issue)
    I was not able to reproduce results with this veulnerability (IE6 SP1). Please comment if you can reproduce it. If it is indeed true, it would allow an attacker to run an executable on the user's system. The user would have to click "open" on an HTML file download. Security warnings would not be displayed.

    "BackToFramedJpu - Cross-zone scripting(requiring a subframe in victim page)"
    Moderate
    This could allow an attacker to execute code in another security zone. It could potentially be used to execute code in the "my computer" zone if the attacker knows the location of a local page with frames.

    I'll comment on the rest later.

  23. Code reuse is code reuse by Grizzlysmit · · Score: 3, Insightful
    This is not the design methodology used in the *nix world.
    Code reuse is code reuse, whether it is Windows, Unix, or any other OS/app. Modern programmers are taught to do code reuse, and saing "This is not the design methodology used in the *nix world" is plain stupid.

    Hmmm who modded this troll up as Interesting, ok I'll pretend this is not a troll, and answer, what M$ has done with bimbo's and IE is not just code reuse, they have not just used some of the same libraries again, they have tightly coupled, them together, so that they cannot easily be separated, parts of windows code was put into the IE libraries, were it doesn't belong in order to legitamise their claim that the two are so called integrated, butchered would be a better term, this is why all of a sudden installing IE even without the "IE desktop", changed your system libraries. In addition inorder to further the same goals or out of shear incompetence, M$ have hooked the two together, via global variables and functions to the point where the one cannot exist with out the other. This is not code reuse this is bad design, and infact the oppersite of structured programming, which is the basis of real code reuse.

    When gzip security hole was discovered, it hit hundreds of Unix applications, because they reused the code from this library. Is the "design methodology" any different?

    The gzip bug demonstrated that it sometimes can even be worse on *nix, due to source code coping instead of shared libs, so that the bug had to be fixed in multiple places.

    You really don't know the first thing about coding do you, when you use a library you do not cut and paste the code into your own, you use their functions and stuff, so all that had to happen with gzip was they fixed the library, then if another project was staticly linked to the library it would have had to be relinked to the new library, but as the majority of code is dynamically these days, most programs would only need you to update the dynamic library on your system, and whala, all programs using the library are fixed next time you run them.

    just a hint: don't lambaste an other person for ignorance in an area you don't have a clue about, some of us make our living programming seeing you make unkind comments to someone else just for being right pisses us off.
    --
    in my life God comes first.... but Linux is pretty high after that :-D
    Francis Smit
    1. Re:Code reuse is code reuse by mentin · · Score: 4, Insightful
      You really don't know the first thing about coding do you, when you use a library you do not cut and paste the code into your own, you use their functions and stuff

      And you don't know anything about gzip vulnerability and instead generalize your ideas of how it should be to how it is actually done.

      Lots of applications were using customized version of gzip, e.g. Linux kernel used a trimmed down version of gzip. They could not be simply recompiled with new library - the bug had to be fixed in every copy of the source code - yet, it was code reuse via copy/paste as much as it could possibly be. Too little applications used shared library, so even those application that used standard gzip had to be rebuild with new static library.

      And if *nix world moves to using shared libraries more, it will face the same problem Microsoft has - a single security fix in a single shared library can potentially break any of hundred applications that use this library, and all these applications has to be tested with patched version. Which is still better than patching hundred applications independently.

      --
      MSDOS: 20+ years without remote hole in the default install