Slashdot Mirror


Exploit Based On Leaked Windows Code Released

mischief writes "A post to Bugtraq from SecurityTracker.com reports an Internet Explorer 5 exploit that has been released based on the Win2K code leak: 'It is reported that a remote user can create a specially crafted bitmap file that, when loaded by IE, will trigger an integer overflow and execute arbitrary code.' Only affects IE 5 apparently, but still - it didn't take long!"

952 comments

  1. Open Source More Secure... maybe not by LostCluster · · Score: 5, Insightful

    Oops... we just gave MS a chance to say keeping the source secret keeps flaws like this secret as well. :)

    1. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 5, Insightful

      > Oops... we just gave MS a chance to say keeping the source secret keeps flaws
      > like this secret as well. :)

      Yeah, but if Windows were truly open source then there's not chance it'll just be sat on for six months...

    2. Re:Open Source More Secure... maybe not by The+Unabageler · · Score: 5, Funny

      OTOH M$ should thank the code thiefs for expediting their QA process :-)

      --
      perl -e '$_="\007/4`\cp%2,".chr(127);s/./"\"\\c$&\""/gees; print'
    3. Re:Open Source More Secure... maybe not by aborchers · · Score: 5, Insightful

      Funny, yes, but in the interest of full disclosure it's worth noting for the credulous that this code was perhaps only vulnerable because it had not been open for audit before.

      In other words, had the source code for IE been OSS from day one, then the bug might very well have been found and fixed before the application was widely distributed.

      --
      Trouble making decisions? Just flip for it.
    4. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 2, Insightful

      Finding flaws in IE5 from the source code is like a novelty. I'd rather people work on breaking IE5 than breaking IE6. Their code will never be secure, regardless of who has the source.

    5. Re:Open Source More Secure... maybe not by 1010011010 · · Score: 5, Funny

      Finally, Microsoft's "Trustworthy Computing" exercise begins in earnest.

      Hehe

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    6. Re:Open Source More Secure... maybe not by mattdm · · Score: 3, Interesting

      That's exactly the point -- it's impossible to keep source code secret, as this proves.

    7. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 4, Insightful

      "Oops... we just gave MS a chance to say keeping the source secret keeps flaws like this secret as well. :)"

      Who says it was secret? For all you know, it could have been the cause of that "mysterious intrusion" a few years ago...

    8. Re:Open Source More Secure... maybe not by orthogonal · · Score: 2, Interesting

      Oops... we just gave MS a chance to say keeping the source secret keeps flaws like this secret as well. :)

      And you guys moderated this post of mine funny.

      Bwah-hahah-ha!

      Yeah, Ok, I was trying to be funny, but I guess I underestimated the truly innovative quality of Microsoft's incompetence.

    9. Re:Open Source More Secure... maybe not by LostCluster · · Score: 4, Insightful

      On the other hand, this bug existed in IE5 all along, but was not discovered until the code was leaked. Now, IE6, which is not at risk, has far surpassed the at-risk version in usage.

    10. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 5, Insightful

      Open-source security doesn't come from having the source available. It comes from lots of people actively working on the source. Tell me, how many random hackers do you think will work on the Windows codebase?

      This is one of the reasons why "open source" is more than "source available"

    11. Re:Open Source More Secure... maybe not by marktoml · · Score: 1

      so you're saying: "Information wants to be free" :)

    12. Re:Open Source More Secure... maybe not by aborchers · · Score: 5, Insightful

      A valid observation, but how many exploits were found without access to the source? If that number were low, the security-through-source-obscurity would be valid, but unfortunately for MS's credibility, it isn't low.

      It just turns out this one was extra easy to find because the code could be read. It would have been equally easy to fix as to exploit (had non-assholes been reading the source, but fear of contamination is keeping most credible OSS engineers from touching that stuff with a 10-ft debugger), bringing us right back around to the superior security of open-source position.

      --
      Trouble making decisions? Just flip for it.
    13. Re:Open Source More Secure... maybe not by Bender+Unit+22 · · Score: 3, Insightful

      Bah, I am sure they will always manage to turn it around.

      No exploits = Our software are the best no-one has been able to find anything.
      Exploit made= Access to source code are dangerous.

    14. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 4, Insightful

      You have to remember that this exploit has already been fixed. As:-

      Only affects IE 5 apparently

      shows.

    15. Re:Open Source More Secure... maybe not by Short+Circuit · · Score: 5, Insightful

      It seems so obvious to someone who's been using OSS for years.

      Linux source code has been around for how long? An how many exploits have been released for it?

    16. Re:Open Source More Secure... maybe not by n3k5 · · Score: 1
      Oops... we just gave MS a chance to say keeping the source secret keeps flaws like this secret as well. :)
      ... which would in turn give others a chance to explain why this argument is bullshit. At least since the recent scandal about the flaw that was in the wild and also known by MS for six whole months, the press is less MS-friendly and does give critics a voice as well in their coverage. (Well, you know that, obviously, I'm just elaborating a little here.)
      --
      but what do i know, i'm just a model.
    17. Re:Open Source More Secure... maybe not by yamla · · Score: 5, Insightful

      What evidence do you have that this bug was not found until the code was leaked? It is entirely possible that some people did indeed know about this bug and had used it to exploit Windows systems for quite some time. Of course, I have no evidence of this either but as I'm not a black-hat (or indeed a hacker at all), I wouldn't expect to hear about it.

      --

      Oceania has always been at war with Eastasia.
    18. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      Microsoft might actually benefit from this leak. Security problems will be spotted and fixed faster, and Windows will become "more secure", as Linux has become due to source code being available.

    19. Re:Open Source More Secure... maybe not by Serveert · · Score: 2, Interesting

      Or, you can say that it's impossible to keep the source closed up in today's world of outsourcing, irate employees and whatnot. So the best way to adapt is to keep it open so there are no surprises. ;)

      --
      2 years and no mod points. Join reddit. Because openness is good.
    20. Re:Open Source More Secure... maybe not by kawika · · Score: 1
      It comes from lots of people actively working on the source. Tell me, how many random hackers do you think will work on the Windows codebase?
      I think a lot of hackers would "work on" Windows code. Unfortunately, for most their goal would be to spread viruses and spyware for financial gain, not to improve the code.
    21. Re:Open Source More Secure... maybe not by essreenim · · Score: 1

      Yeah,

      Accept, if it was open source in the first place,

      bugs like this would have been found before Win2K was even released!!!

    22. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 4, Interesting

      Now, IE6, which is not at risk, has far surpassed the at-risk version in usage.

      References, please. I know of some companies that will NOT move to IE 6.0 because of increased vulnerabilties that do not exist in 5.0 or 5.5. I myself have had bad experiences with IE 6.0. Where did you get your facts?

    23. Re:Open Source More Secure... maybe not by diersing · · Score: 4, Insightful
      Where can I download the patch for IE5?

      Just because it doesn't occur in future releases, doesn't mean its been fixed. Unless your arguing that staying current is the only way to avoid exploits, then your making a strong argument that the TCO of Open Source should be sung from the moutain top.

    24. Re:Open Source More Secure... maybe not by malfunct · · Score: 5, Interesting

      These "easy to find" bugs were probably fixed in the huge code audit that MS did as part of thier security initiative that happened AFTER the date of the leaked code.

      Not to say your point isn't valid, just that the real question is how do you get more intelligent eyes reading the code looking for this stuff. OSS isn't necessarily better, its just that highly popular projects have lots of eyes. I know plenty of projects that get far fewer eyes and have TONS of bugs. Now that MS is being forced to be secure they are having lots of eyes so we will see in longhorn if this improved anything.

      I will say this, its easier to trust something that you can look through yourself, it may not be safer but you like it better because if you wanted you could see what was wrong. Its like driving a car vs riding with someone. You are often more at ease when you are behind the wheel because you can see/make/correct the mistakes whereas with another person driving you just have to trust. It has nothing to do with which driver is better.

      I will say that linux and apache are just great projects with hoards of great developers. Its a testament to the possiblities of the open source model, but its not proof that the model is better. There are plenty of OSS projects that just suck, and those don't show me that the model is broken.

      Finally I will say there isn't the same incentive to make perfect code in a corporation that there is in the OSS community. The corporation is only going to do enough to get th money rolling in because the money is the reward. The OSS programmer is going to write to the very best of his ability because the code itself is the reward. Still doesn't make one model necessarily better than the other. The way we will make microsoft improve its products is quit upgrading until they can prove they have a superior product. It seems from the press releases that the pressure of Linux may actually be forcing MS to improve.

      --

      "You can now flame me, I am full of love,"

    25. Re:Open Source More Secure... maybe not by B3ryllium · · Score: 2, Insightful

      Eleven years. Dozens of exploits, perhaps hundreds.

    26. Re:Open Source More Secure... maybe not by Serveert · · Score: 2, Interesting

      Or, you can say that keeping the source locked down is impossible these days given irate employees and outsourcing.

      --
      2 years and no mod points. Join reddit. Because openness is good.
    27. Re:Open Source More Secure... maybe not by El · · Score: 4, Interesting
      More importantly, what would be Micrsoft's reaction if you sent them a note saying "By the way, do you guys know there is a buffer overflow problem in IE5?


      My guess is they would say "We don't support IE5 amymore. Upgrade to IE6SP1". Followed by legal action against you for disclosing M$ trade secrets.

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    28. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      Got the exploit, ran it on a system of mine (Win98se, IE 5.5 SP2) and nada, zip, nothing. No crash, no blue screen.

    29. Re:Open Source More Secure... maybe not by tedgyz · · Score: 4, Insightful

      Your last point is particularly poignant. I followed the link, started reading, and then saw there was source code in it. I quickly x'ed the tab to avoid even glancing at the code.

      The editors should add an update warning that some source code is in the article. It's like seeing your sister naked. Ack!

      Obligatory Monty Python reference:
      GOD: ...What are you doing now!?
      ARTHUR: I'm averting my eyes, oh Lord.
      GOD: Well, don't. It's like those miserable Psalms -- they're so depressing. Now knock it off!

      --
      "No matter where you go, there you are." -- Buckaroo Banzai
    30. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 1, Insightful

      Sendmail source code has been around for how long? 20 years? Is it fixed yet? Not really.

      OK, how about Bind?

      Conclusion: It has a lot more to do with the code quality and the function of the software than it does with "Open Source".

    31. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 1, Insightful

      MS's customers have been doing their QA for years and paying hard-earned money for the pleasure.

    32. Re:Open Source More Secure... maybe not by slipandfall · · Score: 4, Insightful

      That's exactly the point -- it's impossible to keep source code secret, as this proves.

      Ummm. You need to go back to logic class. This doesn't prove that it's impossible to keep source code secret at all. That would be like saying that the fact that I got a ticket on my way to work this morning proves that it's impossible to speed without getting a ticket. It doesn't follow.

    33. Re:Open Source More Secure... maybe not by OsCarJ · · Score: 5, Funny

      It's like seeing your sister naked. Ack!

      I don't know. I always thought your sister was pretty hot.

    34. Re:Open Source More Secure... maybe not by NatasRevol · · Score: 0

      What part of IE 5.0 do you not understand???

      --
      There are two types of people in the world: Those who crave closure
    35. Re:Open Source More Secure... maybe not by GlassHeart · · Score: 5, Insightful
      Just because it doesn't occur in future releases, doesn't mean its been fixed. Unless your arguing that staying current is the only way to avoid exploits, then your making a strong argument that the TCO of Open Source should be sung from the moutain top.

      You're right, but open source software don't all conveniently provide security updates for old versions, either. It is definitely better, because if nobody else (package maintainer) does it for you, you can do it yourself. However, let's not sing from the mountaintops, because the TCO for insisting on running Red Hat 5.0 today is probably considerable.

      Both forms of development obey the same equation: cost versus benefit. The difference is that the cost in commercial software is entirely calculated based on the perspective of the source code owner. While open source is better, it can still be "too expensive" to fix relative to just upgrading.

    36. Re:Open Source More Secure... maybe not by fetus · · Score: 3, Funny

      The patch is called "IE 6"

    37. Re:Open Source More Secure... maybe not by Vargasan · · Score: 4, Insightful

      "TCO for insisting on running Red Hat 5.0 today is probably considerable."

      Hmm, Windows 2000 comes with IE 5.0. My Windows 2000 with slipstreamed SP3 still has IE 5.0. Not to mention, I still have IE 5.0 installed, because I don't use IE.

      How many places do you know still have Windows 2000 compared to places with Red Hat 5.0?
      Exactly.

      Maybe you should compare it to a relatively new Red Hat version, like 7.3 or say 8.0.

      --
      Putting the romance back into necromancer.
    38. Re:Open Source More Secure... maybe not by ajs · · Score: 5, Insightful

      Let's make this clear: the value of open source to security is not that there are this passive pool of eyes waiting to look at all code, but rather that when you have the eyes, they already have the code.

      How is this practical? Look at Linux, and more specifically Red Hat. There was a period of a year or two where Red Hat was finding a TON of bugs and fixing them. Why? Because they paid an external auditing firm to find them.

      This seems like business as usual until you think about the SuSE user... he gets a security update to openssh and sendmail even though HIS vendor didn't do the audit. This idea that everyone benefits whenever ANYONE in the community does the right thing means that the right thing gets done far more often. It's not that Linux vendors are more security conscious, it's that there are more of them.

      When Microsoft gets around to doing a security audit that's great, but they don't benefit when Red Hat does one or when FreeBSD does, etc., and that's hurting them and their reputation.

    39. Re:Open Source More Secure... maybe not by James+Wright · · Score: 1

      Yeah, if Microsoft released their source code, billions of new viruses would be created to exploit Microsoft's poor code.

    40. Re:Open Source More Secure... maybe not by dbkluck · · Score: 4, Insightful

      What's more secure, secret flaws or no flaws at all? I don't see how MS has a leg to stand on. This bug has been there--presumably unnoticed--for literally years. Within a matter of days of the source code's being "released," it has been identified, and if the MS developers were anything like OSS developers (i.e. didn't have some ridiculous "200 day" fix policy) it would be fixed in a matter of a few more days. I can't see how this is anything other than a vindication of the OSS model.

    41. Re:Open Source More Secure... maybe not by Short+Circuit · · Score: 3, Insightful

      The larger a project is, the more eyes get focused on improving it. The Linux kernel has had a great deal of fanatical attention, so a lot of people are dedicated to keeping it great.

      Besides, if Sendmail lets someone into the system, or bind, UNIX permissions and Access Control Lists help keep the infection from spreading. The developers aren't under an insane amount of pressure to get it right every time. They can get lazy. Or something.

      Heh. The kernel doesn't have anything to fall back on, so kernel developers aware of their responsibility are under stupendous pressure to get it right every time, despite the peer-review process. Hehe. That kind of pressure makes you crazy. Makes you fanatical. heh. Makes you work harder. Makes a good crazy, you know?

      (disclaimer: I'm not a kernel developer (yet)... but I don't mind being crazy. Heh.)

    42. Re:Open Source More Secure... maybe not by imnoteddy · · Score: 5, Interesting
      What evidence do you have that this bug was not found until the code was leaked?

      I worked at MS once (hated it, quit) and the bug tracking system had a category of "won't fix" bugs - bugs they knew about but had no intention of fixing.

      --
      No electrons were harmed creating this post, though some may have been subjected to electrical and/or magnetic fields.
    43. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      "Where can I download the patch for IE5?"

      http://www.microsoft.com/windows/ie/downloads/cr it ical/ie6sp1/default.asp

      *snicker*

    44. Re:Open Source More Secure... maybe not by ostrich2 · · Score: 1, Funny

      I think you misunderstand: he's talking about your sister.

    45. Re:Open Source More Secure... maybe not by KReilly · · Score: 5, Interesting

      But I think the point is that it was leaked. That nobody can keep an eye on their code if it is used this widely. If the code had been under public scrutiny since day one, more flaws would be found, but the overall code would be stronger, not weaker. This is why everyone can complain about tons of holes in linux, but miss the fact that just as many (if not more) exist in windows, and its just a matter of time before they get found out. With Linux, you have to take the additude, the sooner, the better.

    46. Re:Open Source More Secure... maybe not by drinkypoo · · Score: 1

      Actually, I suspect a lot of random hackers would be willing to work on the Windows codebase if it were Open. In fact, I'd bet that even if you weren't allowed to use the code you wrote elsewhere, some people (like, windows programmers) would be dashing off patches to the OS and tools fairly frequently, if Microsoft would give them source access, and accept their patches.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    47. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      My point would be "exactly how secure can their software be when they can't even keep their CODE ITSELF secure?!"

    48. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      How about IE 5.5?

      Can be downloaded here.

      That's not vulnerable either.

      You have to remember that the source code that was made available was pretty damn old, and hadn't undergone four or so years of patching.

    49. Re:Open Source More Secure... maybe not by G.+W.+Bush+Junior · · Score: 5, Insightful

      I know plenty of projects that get far fewer eyes and have TONS of bugs.


      it's a pretty moot point

      The impact of a bug i probably inversely proportional to the amount of people auditing the code in an open source project...
      Sure, there are a lot of small projects that nobody really uses, so there aren't that many eyes for auditing the code... but so what?

      The projects are unpopular, so if somebody found a security bug it wouldn't affect that many people (and is it really worthwhile spending the time making an exploit that will affect 1000 users worldwide?)

      As long as the popular projects are safe then I don't really care.

      --
      "I don't know that Atheists should be considered as citizens, nor should they be considered patriots." -George H.W. Bush
    50. Re:Open Source More Secure... maybe not by Paleomacus · · Score: 5, Insightful

      My company has one of these lists as well. I'd bet most companies do.

      Just because someone claims something is a bug doesn't mean that it _is_ and must be fixed.

      A lot of our bug reports are just user preference/pickiness.

    51. Re:Open Source More Secure... maybe not by Cramer · · Score: 3, Interesting

      /me whistles innocently...

      [cramer:ttyp1]dominion:~/[1:38pm]:uname -a
      Linux dominion 2.3.42-SMP #11 SMP Sun Feb 6 20:06:02 EST 2000 i686
      [cramer:ttyp1]dominion:~/[1:38pm]:cat /etc/redhat-release
      release 4.1 (Vanderbilt)

      [ttyp0]foobar:~/[2:46pm]:uname -a
      Linux foobar 2.3.18-SMP #10 SMP Mon Sep 20 17:27:00 EDT 1999 i686 unknown
      [ttyp0]foobar:~/[2:46pm]:cat /etc/redhat-release
      release 5.1 (Manhattan)

      [jfbeam:pts/0]chickenboo:~/[2:11pm]:uname -a
      Linux chickenboo 2.4.2-SMP #1 SMP Tue Feb 27 17:04:47 EST 2001 i686 unknown
      [jfbeam:pts/0]chickenboo:~/[2:11pm]:cat /etc/redhat-release
      Red Hat Linux release 6.2 (Zoot)


      (And no, they are not publically accessible machines.)

    52. Re:Open Source More Secure... maybe not by Eric+Savage · · Score: 5, Insightful

      And that's just Linux. There have been gobs of them for the various popular software packages out there (Apache, Samba, PHP, etc). I try to stress to other developers that OSS isn't necessarily more secure, its more prone to security, a fine line that can be very significant. I am hugely in favor of OSS, but the idea that opening crappy source means other people will fix your bugs is as false as the idea that opening unfinished source means other people will finish it.

      --

      This is not the greatest sig in the world, this is just a tribute.
    53. Re:Open Source More Secure... maybe not by sjames · · Score: 1

      Furthermore, the knowledge from the start that the code WILL be public changes the implementation of seurity. While it is always best from a seurity standpoint to assume that an attacker WILL have access to the code, in a proprietary environment, it's just too easy to fall into the habit of assuming it is and always will be a secret. That naturally leads to implementations that rely on obscurity.

      That is a mistake that simply doesn't happen to a security conscious OSS developer. The very nature of the projet makes the faulty assumption obviously false.

    54. Re:Open Source More Secure... maybe not by niittyniemi · · Score: 1

      > Now, IE6, which is not at risk, has far surpassed the at-risk version in usage.

      ...and in bugs... :)

      --
      The Machine stops.
    55. Re:Open Source More Secure... maybe not by GlassHeart · · Score: 3, Insightful
      Maybe you should compare it to a relatively new Red Hat version, like 7.3 or say 8.0.

      That's the entire point I was making, which you apparently missed. Just because Red Hat 5.0 was open source doesn't mean you can viably continue to use it indefinitely. If nobody will apply patches for you for free, you'll either have to do it yourself (time) or pay somebody to do it (money). Remember, the cost in this case is not compared to Windows, but to upgrading.

      But just for the sake of argument, where would you get free patches for Red Hat 7.3?

    56. Re:Open Source More Secure... maybe not by abischof · · Score: 1

      References, please.

      IE 6.x has about 75% of the browser market; IE 5.x has about 17%.

      --

      Alex Bischoff
      HTML/CSS coder for hire

    57. Re:Open Source More Secure... maybe not by mdpye · · Score: 4, Insightful

      Yes, look at open source bugzillas, they have them as well. That category is for bug reports which aren't really bugs in the eyes of the maintainer.

      I'm not saying that MS might not throw a lot of remote root vulnerabilities in that category too, I don't have access to their bug db!

      MP

    58. Re:Open Source More Secure... maybe not by drinkypoo · · Score: 4, Informative

      Here's a nice supporting example for you: One of my buddies brought up a machine, got a DHCP response from the wrong place, and got railroaded to some site that looked like it was selling knives, instead of windows update. Turned out it was a page with a DSO exploit in it, and he got owned, had to reinstall the box. (And go track down the bozo advertising bad DNS in his DHCP.) It was ye olde DSO exploit. So someone installing (for whatever reason) something with IE5 can be taken over quite ruthlessly, especially since all you need do is show them an image.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    59. Re:Open Source More Secure... maybe not by arkanes · · Score: 4, Insightful

      You're correct. The proper way of phrasing this would be "As this proves, it's irresponsible to assume that the source will always be secret".

    60. Re:Open Source More Secure... maybe not by SydShamino · · Score: 2, Informative

      Well, the first google search result for '"redhat 7.3" security update' yields: this link where a security bug in 7.3 is patched. That bug fix was released less than 15 days ago, so it seems like it still gets support.

      I appears to come from the Fedora team.

      --
      It doesn't hurt to be nice.
    61. Re:Open Source More Secure... maybe not by sterno · · Score: 4, Insightful

      Not to say your point isn't valid, just that the real question is how do you get more intelligent eyes reading the code looking for this stuff. OSS isn't necessarily better, its just that highly popular projects have lots of eyes. I know plenty of projects that get far fewer eyes and have TONS of bugs. Now that MS is being forced to be secure they are having lots of eyes so we will see in longhorn if this improved anything.

      Open source scales well. A small project that few people take an interest in has few users and lots of bugs. It's not a big problem if the bug is exploited because only a handful of people are even using it.

      As more people use it and more people get involved more people see the code. As more people see the code, more bugs are eliminated and the code becomes better. Thus the risk of serious bugs declines as more people use the software.

      In the case of a closed source product though, the scrutiny does not scale at all. The scrutiny is a fixed value based on the company's internal policies. Given that most companies are far more concerned about time to market and profit margins, extensive security audits are seen as unneeded costs. As the product becomes larger and more complex, the likelyhood of bugs developing increases, but the likelyhood of a thorough review remains constant or even declines.

      --
      This sig has been temporarily disconnected or is no longer in service
    62. Re:Open Source More Secure... maybe not by tgibbs · · Score: 1

      Just because it doesn't occur in future releases, doesn't mean its been fixed

      Then nothing can ever be fixed, unless Microsoft invents a time machine. Until then, the next best thing is to supply a free upgrade that lacks the bug, and that has already been done.

    63. Re:Open Source More Secure... maybe not by vondo · · Score: 4, Insightful
      I think the point is that the fix for the bug may not have been applied, but the exploit may not work (or a different exploit would be needed) because the whole binary might have changed a little.

      When an exploit is found for, say, the Red Hat 7.3 kernel, it may not work on Red Hat 8.0 let alone Debian for just this reason. That's not to say the bug isn't present in all three.

    64. Re:Open Source More Secure... maybe not by ktulu1115 · · Score: 1

      Correct, IIRC from my discrete analysis class the proper term is "fallacy to prove the hypothesis".

      --
      # fuser -v /dev/attention | grep work
      #
    65. Re:Open Source More Secure... maybe not by OsCarJ · · Score: 0, Offtopic

      You stay the hell away from my sister you pervert!

    66. Re:Open Source More Secure... maybe not by ktulu1115 · · Score: 1

      Very important point. Mod parent up, I would but just ran out.

      --
      # fuser -v /dev/attention | grep work
      #
    67. Re:Open Source More Secure... maybe not by atallah · · Score: 4, Informative

      Actually, 5.5 appears to be vulnerable. I loaded the BMP and BOOM! it crashed.

    68. Re:Open Source More Secure... maybe not by edxwelch · · Score: 2, Interesting

      "These "easy to find" bugs were probably fixed in the huge code audit that MS did as part of thier security initiative that happened AFTER the date of the leaked code."
      This is just speculation, besides, if they found a security hole in IE5 it would be their responsibiltiy to published the fact rather than leave IE5 users out there vunerable.

    69. Re:Open Source More Secure... maybe not by miu · · Score: 1
      Now, IE6, which is not at risk, has far surpassed the at-risk version in usage.

      So lets do a wild ass guess and say IE5.0 has a 10% market share at this point. The delivery techniques used by email worms could make sure that nearly the entire vulnerable population is exposed to the exploit, have the exploit code register its host with a simple port listener machine and the bad guy winds up with a list of exploitable machines.

      I'd be willing to bet that someone is working on a delivery system and support tools for the exploit at this very moment.

      --

      [Set Cain on fire and steal his lute.]
    70. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 1, Insightful

      Win2k is still bought and used. Win2k has IE 5.0 installed by default.

    71. Re:Open Source More Secure... maybe not by malfunct · · Score: 1

      I don't actually know this, but wasn't one of the critical updates released on windows update one that moved you over to IE6, in which case IE6 is the fix for IE5 vulnerabilities.

      --

      "You can now flame me, I am full of love,"

    72. Re:Open Source More Secure... maybe not by 1010011010 · · Score: 5, Funny

      60% Funny
      20% Troll
      10% Insightful

      Welcome, Microsofties!

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    73. Re:Open Source More Secure... maybe not by zurab · · Score: 1
      Just because someone claims something is a bug doesn't mean that it _is_ and must be fixed.

      A lot of our bug reports are just user preference/pickiness.

      But most of those usually belong to a separate category called "feature enhancements" or something similar. Ahh... the irony.
    74. Re:Open Source More Secure... maybe not by gehrehmee · · Score: 1

      Somebody hasn't been paying attention.

      Everybody complains about the obselesence of Debian's stable releases. What they rarely mention is that there are constant updates. They don't add features (because those new features neccesarrilly add a risk of new bugs), but only fixes for existing security problems.

      --
      "You know, Hobbes, some days even my lucky rocketship underpants don't help" -- Calvin
    75. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0, Troll

      So someone who worked for M$ and had source code access could have been using this exploit for years! Just because it is found today by someone willing to expose it instead of exploiting it only makes the M$ position worse. JUST HOW MANY OLD, SERIOUS BUGS ARE IN WINDOWS?

    76. Re:Open Source More Secure... maybe not by Ugot2BkidNme · · Score: 2, Informative

      I am still using Redhat 5. have custom software written by people who are no longer here and when it was upgraded to 7.3 it broke so I am still running 5.0 until we have the resorces to fix teh software.

    77. Re:Open Source More Secure... maybe not by WNight · · Score: 4, Insightful

      Part of the reason old systems don't get new OSes is that they don't need them enough to justify the cost.

      You can download RedHat 9 (10?) and upgrade some or all of your ailing RedHat 5.0 box. Either upgrade the whole thing (RH9 would do slim installs suitable for old machines) or just upgrade the old service.

      Call Microsoft and ask them if they allow free upgrades to WinXP from older OSes to fix security problems. Ask if they mind if you grab some WinXP DLLs from a friend and use them on your WinNT machine. That is, if they would work. Services in RedHat would probably work on an older machine, though they may require a parallel install of some libraries.

      Then there's the issue that even for outdated versions of software that aren't patched directly, a moderately skilled coder (perl - barely any C - like many junior unix admins) can usually adapt the fix for an older version, or use the information provided to script some firewall rules to avoid it.

      Then there's simply the fact that it's available. Even if you can't do it internally, you can pay a coder for a day of work ($250 tops - about the cost of a trouble call with big software companies) who can go grab all the source code (no NDAs required) and do the fix for you.

      If this IE5.0 fix was critical for you to have, how could you go about getting it before Microsoft got around to fixing it? Turn off images?

    78. Re:Open Source More Secure... maybe not by chrootstrap · · Score: 1

      Really? While the red security flag has been raised lots of times for things in Linux, I've only seen a handful or two exploits for the kernel itself. There are indeed hundreds for the various commonly-used software packages, of course.

      Could you give some examples?

      --
      Hacking articles at http://www.geocities.com/chroo
    79. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      Yeah, but be clear on one thing -- Sendmail is the most popular piece of Unix software in history. It's a critical piece of infrastruture that often runs partially as root (so much for ACLs). The source has been reviewed by thousands of people.

      Don't buy ESR's moronic crap about Open Source being a magic bullet. The "secure" OSS stuff is that way because the project leaders are good coders.

    80. Re:Open Source More Secure... maybe not by bach37 · · Score: 4, Funny

      Where can I download the patch for IE5?

      The Patch.

      Scott
      (Come on, you knew this answer was coming!)

    81. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      > because of increased vulnerabilties that do not exist in 5.0 or 5.5.

      That's rather dumb thinking. Security Experts generally only target the latest and greatest -- just because nobody reports vulnerabilties in 5.x doesn't mean they don't exist.

    82. Re:Open Source More Secure... maybe not by __past__ · · Score: 1

      On the other hand, most open source bugzillas do at least let you look at all the current security-related bugs. They do not hide them from a concerned user's view, like Microsoft and Mozilla do.

    83. Re:Open Source More Secure... maybe not by Russ+Nelson · · Score: 1

      Hordes. Hordes of developers. Mnemonic: Hordes of open source developers don't hoard.
      -russ

      --
      Don't piss off The Angry Economist
    84. Re:Open Source More Secure... maybe not by lseltzer · · Score: 1

      >>It is entirely possible that some people did indeed know about this bug and had used it to exploit Windows systems for quite some time.

      This is just as possible with open source software. As long as someone else doesn't notice it it's your bug to exploit.

    85. Re:Open Source More Secure... maybe not by lseltzer · · Score: 1

      No, it's all the 5.x versions, up to and including 5.5 SP2

    86. Re:Open Source More Secure... maybe not by rixstep · · Score: 1

      In other words, had the source code for IE been OSS from day one, then the bug might very well have been found and fixed before the application was widely distributed.

      Apples & oranges. That works in the Linux OSS world, but not in the Microsoft world. Microsofties are generically not terribly talented. They're not groomed for their work. They 'wing it' from day one. The entire atmosphere is counter-productive.

      You're assuming that other Microsofties would have found the error? You flatter Microsoft.

    87. Re:Open Source More Secure... maybe not by B3ryllium · · Score: 1

      RedHat.

    88. Re:Open Source More Secure... maybe not by chrootstrap · · Score: 1

      lol... maybe, they change the name to BlackHat.

      --
      Hacking articles at http://www.geocities.com/chroo
    89. Re:Open Source More Secure... maybe not by chance2105 · · Score: 0



      Ok, kids, give me a break. Comparing the security of programs running on Windows to the security of programs running on Linux is like comparing apples to oranges. Exploits in the Linux kernel notwithstanding -- a security hole in a program run by a regular user *will not* have the ability to trash a system or do anything that it is not given permission for. Under Linux, a runaway Mozilla program that's running behind iptables can do .. what? Precisely nothing.

    90. Re:Open Source More Secure... maybe not by DebianRcksLindowsLie · · Score: 1

      There isn't a patch for the new exploit, and MS doesn't plan to support this, either. They only support IE6.

      --
      Sick of people trashing Debian? So am I. Read the article in my sig to find out how to stop the worst offender.
      Check my homepage to find out more on the brains behind the Debian trash talk.

    91. Re:Open Source More Secure... maybe not by iamacat · · Score: 1

      It's not so simple. Say I find out that a web store uses a particular "small project" web module. I can then read the source code, find a way to get in and steal their credit card database. If it was a closed source component with a small user base, the barrier would be higher.

    92. Re:Open Source More Secure... maybe not by dasmegabyte · · Score: 1

      Well, to a point it is. The OSS model is fairly myopic...it ONLY cares about the resolution of bugs in code. Code, however, is only the first in a dozen steps to making software available. Most of the world does not care if the "code" has been fixes -- they don't want to download the source and recompile their software and time there's a problem. So after coding the bugfix, there's reversioning, compilation, unit testing, release documentation, the training of tech support, the training of end users, and the mass installation of the package on every machine.

      In short: each commercial bugfix takes a lot more work than what the OSS model provides. OSS eliminates the bug quickly in the codebase, but for all we know, Microsoft does that too. They might have fixed it, passed through unit testing, and on to a patch guy. The patch guy released a patched DLL, and there it sat, like the ark of the covenant, because no product manager in their right mind would ask millions of Windows users to download a program and patch their machines, prompting millions of support calls and the odd botched install, just to prevent somebody from crashing an unused browser.

      This is the kind of bug that gets fixed in the next release unless people ask for it. And it did get fixed in the next release. Why would you want to perform all that work to fix a bug for which there was no known or useful exploit?

      Still, windows security is getting a lot better at making these kinds of fixes now that the automatic update function is available. In fact, since we started enforcing its use at my office, we haven't seen a single problem due to bug exploits. And I haven't had to spend any time patching machines. Something to be said for that, right?

      --
      Hey freaks: now you're ju
    93. Re:Open Source More Secure... maybe not by rezac · · Score: 0

      Who's to say that this hasn't already been exploited? Even by M$ themselves...(not meant to be flamebait). Why broadcast (worms, etc.) these exploits, when they can be kept for "use" at a later time. If this is sounding paranoid, then so be it. zac I don't have a sig yet.

      --
      -- my sig got /.'d
    94. Re:Open Source More Secure... maybe not by malfunct · · Score: 1
      This will be more or less true under properly configured win2k as well. Services run in a machine account with minimal privledges and applications should run in a useraccount with minimal privledges.

      The problem with windows wasn't that it couldn't be configured securely (expliots excluded) its that it wasn't configured securely.

      --

      "You can now flame me, I am full of love,"

    95. Re:Open Source More Secure... maybe not by jimmyharris · · Score: 4, Informative

      I would (and do) use the Fedora legacy project.

      What version of RHL and FC will be supported, and for how long?

      We are currently supporting Red Hat Linux 7.2, 7.3, and 8.0 as these have reached their End-of-Life (EOL).

      When Red Hat Linux 9 becomes EOL on April, 31 2004, we will start legacy support for it as well.

      As Fedora Core releases become EOL, we will provide support for them on a 1-2-3 and out policy, providing for roughly 1.5 years of update support for each release.

    96. Re:Open Source More Secure... maybe not by argel · · Score: 2, Informative
      Might be fixed in SP3.

      1.8 Internet Explorer Is Updated with the Service Pack Microsoft Internet Explorer (IE) version 5.01 is now updated only when you install a Windows 2000 service pack, in accordance with the Microsoft support strategy. Windows 2000 SP3 includes all of the fixes released in IE 5.01 with Service Pack 2, plus additional security and functionality fixes that apply to IE and Microsoft Outlook(R) Express version 5.01. For more information about these fixes, see article Q320853, "List of Bugs Fixed in Windows 2000 Service Pack 3," in the Microsoft Knowledge Base.

      --

      -- Argel
    97. Re:Open Source More Secure... maybe not by yamla · · Score: 1

      The difference being that with open-source software, people can legally publish patches (and of course, those patches can be examined by others). This is not an option with Microsoft source code for the majority of people with access to it.

      --

      Oceania has always been at war with Eastasia.
    98. Re:Open Source More Secure... maybe not by Brian+Boitano · · Score: 1

      Buffer overflow problems are trade secrets now?

      --
      What would Brian Boitano do?
    99. Re:Open Source More Secure... maybe not by WesG · · Score: 0, Flamebait

      I would disagree with you there. Just go to microsoft.com and download IE6.

      Mozilla is a good alternative, but its not quite as fast as IE6 in rendering web pages. Not to mention its not as mature as IE6.

    100. Re:Open Source More Secure... maybe not by Trejkaz · · Score: 1

      Yeah, because it's just so hard to type "emerge -UD world" to keep up to date.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    101. Re:Open Source More Secure... maybe not by bonch · · Score: 2, Insightful

      What's you're saying is, anyone who feels someone is trolling with a baseless anti-"M$" bash is a "Microsoftie?"

      Isn't that a bit of a tinfoil view of the world?

    102. Re:Open Source More Secure... maybe not by bonch · · Score: 1

      Several. Someone even almost infected the kernel development tree itself through Bitkeeper.

      Go to LinuxSecurity sometime and check out all the endless exploits that are announced for packages whose source code has been available for years.

    103. Re:Open Source More Secure... maybe not by bersl2 · · Score: 1

      They should post a fix accompanying any use of the exploit.

    104. Re:Open Source More Secure... maybe not by AvitarX · · Score: 1

      Whats your availability on your servers if you emerge world regularly?

      and how long are you under a high load as it is happening?

      I have not used Gentoo but am courious about it.

      If it is truley and effecient way to keep my servers up to date and running fast that would be great, but if I regularly need to load the fuck out of my servers and restart services it cannot possibly be that much better even if it is less of my time.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    105. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      Good job MS, you were able to fix a bug before it was even revealed. What about all that time when IE5 was the latest MS had to offer? It's still a bug that could have been exploited, they're just lucky no one had stumbled upon it before.

    106. Re:Open Source More Secure... maybe not by imnoteddy · · Score: 1
      Yes, look at open source bugzillas, they have them as well. That category is for bug reports which aren't really bugs in the eyes of the maintainer.

      Well, these were bugs in the eye of the maintainer. I heard the manager of (one of the applications that is now part of MS Office) say "We'll fix it if enough customers complain about (a specific 'will not fix' bug)".

      --
      No electrons were harmed creating this post, though some may have been subjected to electrical and/or magnetic fields.
    107. Re:Open Source More Secure... maybe not by GlassHeart · · Score: 1
      the Fedora legacy project [is] currently supporting Red Hat Linux 7.2, 7.3, and 8.0 as these have reached their End-of-Life (EOL).

      Red Hat 7.2 was released on October 22, 2001. Who supports anything older than two years and four months?

      As Fedora Core releases become EOL, we will provide support for them on a 1-2-3 and out policy, providing for roughly 1.5 years of update support for each release.

      IOW, they expect you to upgrade within 1.5 years. I believe this also means support for 7.2 will be dropped within three months.

      This is, let me stress, entirely fair. Fedora (or anybody else) doesn't have infinite volunteer resources, and cannot possibly support every old version. I'm not blaming them in any way.

      I'm just saying that at some point it's cheaper for you to upgrade than to insist on running the old version. Even when running open source software.

    108. Re:Open Source More Secure... maybe not by WiPEOUT · · Score: 1

      Don't worry.

      Nobody but you reads the articles on /. anyway.

    109. Re:Open Source More Secure... maybe not by rbanffy · · Score: 1

      Absolutely brilliant!

      The cost of ownership is not only paid at the user-side: The software provider has to pay its share.

      By keeping its software closed, Microsoft, just like any other proprietary software provider, has to bear the full burden of maintaining it and keeping it secure.

      On the other hand, by relying on open-source software, Red Hat, SuSe, IBM, HP, SGI and others, are able to share the cost of maintaining, auditing and debugging it. The sharing of knowledge, code and work results in a very efficient cooperative model.

      The years ahead may prove quite interesting.

      And yes, I know I am a bit off-topic, but this deserved to be highlighted.

    110. Re:Open Source More Secure... maybe not by Sancho · · Score: 1

      You're hurting your own argument in your analogy. IE6 is available for free on Microsoft's website. YOu can download just it or any other update they've released. You can't, as you say, download Windows XP. But the point is, you aren't stuck buying a whole new product just to fix this security vulnerability.

    111. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0
      Got the exploit, ran it on a system of mine (Win98se, IE 5.5 SP2) and nada, zip, nothing. No crash, no blue screen.

      That just shows how unstable Windows is. It can't even reliably run an exploit. Check the cables and try restarting. See if that helps.

    112. Re:Open Source More Secure... maybe not by zoney_ie · · Score: 3, Insightful

      Unfortunately, it is probably a VERY bad idea to be running Win2K without a later version of IE.

      Because regardless of what Microsoft pretend or what others accuse or don't accuse, the fact is that IE has been MADE an integral part of the OS.

      I don't use IE anymore, (Firebirdyfoxchicken has served me well for months now with no hitches) but I STILL keep it up to date. Unfortunately it's essential for sensible operation of Windows.

      IMHO.

      --
      -- *~()____) This message will self-destruct in 5 seconds...
    113. Re:Open Source More Secure... maybe not by Rysc · · Score: 2, Funny

      Yes, but you didn't post the uptimes.

      --
      I want my Cowboyneal
    114. Re:Open Source More Secure... maybe not by JohnGalt00 · · Score: 1

      Replying to your sig:
      So how do you know it was a linux box that leaked? Link please?

    115. Re:Open Source More Secure... maybe not by Myopic · · Score: 1

      yo this guy's user number must be worth some money to a dyslexic satanist somewhere

    116. Re:Open Source More Secure... maybe not by Awptimus+Prime · · Score: 1

      Download a Mozilla installation?

      Regardless, if you have a box that is stuck running an older OS, software build, etc, then it's likely a server. It does not matter what browser you have installed on the box, since you probably shouldn't be browsing the web with it to begin with.

      If it were my network, a server dedicated to a specific task wouldn't have blanket net/proxy access to begin with. Security on the application level is secondary to having it wrapped snuggly in a set of firewall rules; not only to protect the box from outside intruders, but to protect it from a silly admin who wants to browse the web in IE from it.

    117. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      And I've seen plenty of windows software that sucks..your analogy is like MS source code...full of bugs!

    118. Re:Open Source More Secure... maybe not by Trejkaz · · Score: 1

      I don't run a whole lot of servers, but if I did, and they were all the same architecture, and they were in the same location, I would use distcc to distribute the compilation (this feature is built into portage already, setting it up is as simple as emerging it, starting the distccd service and adding two settings to make.conf on the machine which will distribute the jobs) and then install the binary packages on every machine. This would probably be only slightly longer a task, you would need --buildpkg on one machine and --usepkg on all the others.

      That being said, there is word of a new feature in portage which will allegedly upgrade only those services where the upgraded version fixes a known security bug. I'm holding out for that, and will probably automate my upgrades at that point.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    119. Re:Open Source More Secure... maybe not by aborchers · · Score: 1
      You're assuming that other Microsofties would have found the error? You flatter Microsoft.


      Er.. No. If the code were OSS, then it wouldn't have been "Microsoftie" code, but would have been community code.

      I don't get your argument at all.

      --
      Trouble making decisions? Just flip for it.
    120. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      I have a question, if IE6 sucks so bad (mind you I'm no IE fan) then why do so many people get a woody at the idea of it being open source?

    121. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      :::gasp::: You mean linux is NOT gonna save the world ??? YOU CAPITALIST BASTARD !!!

    122. Re:Open Source More Secure... maybe not by syrynxx · · Score: 1

      'got a DHCP response from the wrong place' - 'got railroaded' - 'got owned' - that is an excellent supporting example. Happens all the time. Where did your buddy 'bring up' this machine - a black hat convention wireless network? No properly-administered network has multiple DHCP servers on a single segment, unless it's for redundancy. And since DHCP is a broadcast, that knife vendor must have had a rogue DHCP server on your buddy's network segment (i.e., physically nearby) in order to perpetrate this fictional atrocity. Here's a nice supporting example for you - one of my buddies used Windoze, and left the oven on, and his house burnt down, and his wife left him. Therefore, don't use Windoze or your wife will leave you.

    123. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0
      Turn off images?
      I find it absurd that you would want to turn off images in Microsoft Internet Explorer. Images are powerful representations of ideas and are the very heart of what makes the internet useful.

      Besides, an image is worth a thousand worms.

      Thanks, I'll be here all night because other sites are not very usable with lynx.

      --Shane

    124. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      I knew it! I'm installing linux and then I'll have girls!

    125. Re:Open Source More Secure... maybe not by Cramer · · Score: 1

      okie dokie...

      [cramer:ttyp0]dominion:~/[12:39am]:uptime
      12:39am up 150 days, 10:50, 2 users, load average: 0.02, 0.02, 0.00

      [ttyp0]foobar:~/[1:45am]:uptime
      1:45am up 5 days, 14:07, 2 users, load average: 0.00, 0.00, 0.00

      [jfbeam:pts/0]chickenboo:~/[1:14am]:uptime
      1:14am up 8 days, 53 min, 5 users, load average: 0.00, 0.00, 0.00


      foobar had been powered off for a year -- the power went off during the ice storm of 12/2002, and I left it off. chickenboo had a hardware RAID snafu and "/" disappeared -- it took me a few weeks to get around to fishing everything out of /lost+found

      (Yeah, I need to set their clocks, too.)

    126. Re:Open Source More Secure... maybe not by aztracker1 · · Score: 1

      Well, could set .bmp files to open via a plugin, such as quicktime (which likes to seize images)... as an example.. Also, on win98, ie6 is a free update, and as for anyone running win95, you would have as many issues running a linux distro from 1995.

      --
      Michael J. Ryan - tracker1.info
    127. Re:Open Source More Secure... maybe not by aztracker1 · · Score: 1

      IMO a current browser is a "critical" update regardless of security...

      --
      Michael J. Ryan - tracker1.info
    128. Re:Open Source More Secure... maybe not by minus9 · · Score: 1
      "But just for the sake of argument, where would you get free patches for Red Hat 7.3? "

      Updates for RedHat 7.2 and up.

    129. Re:Open Source More Secure... maybe not by minus9 · · Score: 1
      "Isn't that a bit of a tinfoil view of the world? "

      How does tinfoil view the world?

    130. Re:Open Source More Secure... maybe not by anpe · · Score: 1

      the fact that the exploit only works for IE5 doesn't mean that the same hole doesn't exist in IE6.
      For this kind of exploit, a different compile option or whatever can make it fail.

    131. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      yes you can't prevent to have IE5.0 installed on your computer if you have Win2k...it's the default web browser .

      aurora snow
      aurora
      sylvia

    132. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0
      Slashdot won't report that it was a Linux computer at MainSoft from which the Windows 2000 source code was leaked.
      Computers (let alone OSs) don't leak code by themselves. This is as such irrelevant information.
      Also, the Slashdot article you seem to refer to linked to the eWeek piece in which it was said that the source was "leaked from a Linux computer" (whatever that means). As such, Slashdot (or rather the Slashdot editors) reported it.

      You had better get rid of that trollish signature.
      (Side note : The company from which the leak originated was porting MS Windows software to UNIX (which is why they got a copy of the source). Cheapest way to do that is to use Linux on their computers.)
    133. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      Hah!

      I have Windows XP, and I have a girl!

      I DO have Knoppix and Gamer Morphix on CD though.. :)

    134. Re:Open Source More Secure... maybe not by Magada · · Score: 0

      Who's we? Are you suggesting I stole the code or something? It's people like you that give geeks a bad name.

      --
      Something bad is coming when people are suddenly anxious to tell the truth.
    135. Re:Open Source More Secure... maybe not by robby2 · · Score: 1

      That's not completely true. The bug exists in IE5 which gets installed with W2k. So a clean install of w2k gets this bug installed.
      And because IE is completely integrated into the operating system, the bug may not only manifests itself when browsing the internet, but also when browsing, say a network share?

      Now I think of it, what would happen when a person has the "Enable web content in folders" option set in windows explorer?
      Just browsing over (not explicitly opening) a bmp file shows it as a thumbnail in the web content bar.
      It's quite probable the arbitrary code gets executed this way. Anyone in for a test?

      Bottom line: Not using IE for internet browsing is smart, but you're not completely safe yet...

      robby2

    136. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      How can I install IE 6 on my Windows 95?
      How can I upgrade Windows 95 without paying?

    137. Re:Open Source More Secure... maybe not by kwoff · · Score: 1

      There is a difference though in that MS code wasn't open source all along. Maybe it is analogous to releasing a tame animal into the wild.

    138. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      But what is the cost of upgrading windows compared to upgrading RH, etc?

    139. Re:Open Source More Secure... maybe not by Anonymous Coward · · Score: 0

      and the other 10%? Or is this M$ Math?

    140. Re:Open Source More Secure... maybe not by SiChemist · · Score: 1

      Well, if it's just for the sake of the argument :-)

      http://freshrpms.net/
      http://apt-rpm.tuxfamily.org/
      http://dag.wieers.com/home-made/apt/
      http://atrpms.physik.fu-berlin.de/
      http://www.aucs.org/rpmcenter/rpms.html
      http://www.niemueller.de/projects/extrpms/

      Those were just the ones I have bookmarked. You could find more with a web search.

    141. Re:Open Source More Secure... maybe not by some+guy+I+know · · Score: 1
      IE6 is available for free on Microsoft's website.
      Not for MS-Windows 95.
      --
      Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
    142. Re:Open Source More Secure... maybe not by bonch · · Score: 1

      Computers (let alone OSs) don't leak code by themselves. This is as such irrelevant information.

      It was hacked. Did you not get that implication? Sorry.

    143. Re:Open Source More Secure... maybe not by zero_offset · · Score: 1
      Because regardless of what Microsoft pretend or what others accuse or don't accuse, the fact is that IE has been MADE an integral part of the OS.

      Whoa there, Penguin! It was MS that insisted IE was integrated. It was the DOJ & SIGs who insisted it was not.

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

    144. Re:Open Source More Secure... maybe not by Ironica · · Score: 1

      IE6 is available for free on Microsoft's website. YOu can download just it or any other update they've released. You can't, as you say, download Windows XP. But the point is, you aren't stuck buying a whole new product just to fix this security vulnerability.

      Unless you're running Windows 95, which isn't compatible with IE6.

      You would, in that case, have to buy Windows XP to fix this issue.

      --
      Don't you wish your girlfriend was a geek like me?
    145. Re:Open Source More Secure... maybe not by Ironica · · Score: 1

      Say I find out that a web store uses a particular "small project" web module. I can then read the source code, find a way to get in and steal their credit card database. If it was a closed source component with a small user base, the barrier would be higher.

      So what you're saying is, only open-source your software if it's good... and if it sucks, keep it proprietary? ;-)

      --
      Don't you wish your girlfriend was a geek like me?
  2. huh by Tirel · · Score: 2, Insightful

    Anyway, I took a look, and decided that Microsoft is GAYER THAN AIDS.

    When you break the law and possibly expose thousands of users to a root exploit, at least you could be politically correct about.

    "GAYER THAN AIDS", what the hell?

    I hope they sue him..

    1. Re:huh by LocoSpitz · · Score: 5, Informative

      Do not mod parent down. He's pointing out text found in the article link. That is not flamebait.

    2. Re:huh by Dalcius · · Score: 5, Insightful

      You really are going to try and blame this guy for "possibly [exposing] thousands of users to a root exploit"?

      There are certainly other ways to go about reporting bugs (not that Microsoft will listen to any of them), but blaming the messenger for pointing out that the castle wall is full of holes is a bit misdirected if you ask me.

      Cheers

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    3. Re:huh by iso · · Score: 5, Insightful

      That was interesting to read. It made me wonder who the people are who come up with these exploits. This person is obviously very immature, but also very knowlegable about programming to spot something so quickly in so much code. The question is, is this a ridiculously knowledgable 13 year old, or a well-seasoned older programmer who has the social skills of a 13 year old?

    4. Re:huh by MindStalker · · Score: 3, Informative

      The guy sent mail to securityfocus telling them that there was a hole in windows, he did not spread any virus or use this code malisously. SecurityFocus then published this info, if anyone SecurityFocus is the most liable, though I don't believe either should be.

    5. Re:huh by MindStalker · · Score: 1

      sorry s/SecurityFocus/SecurityTracker/

      zzzzzzzzzzz

    6. Re:huh by Have+Blue · · Score: 1

      On the plus side, I can't wait until theis replaces welcoming our new overlords as the hot Slashdot dead horse joke.

    7. Re:huh by Anonymous Coward · · Score: 2, Insightful

      From a most perspectives, there's no difference. Neither is employable, and neither will have many friends.

      (Hate having to post anonymously, but you have to be careful whose toes you step on.)

    8. Re:huh by Tango42 · · Score: 1

      Or maybe a well-seasoned older programmer with good social skills who told a not-so-knowledgable 13 year old (probably a "script kiddie").

    9. Re:huh by CodeRx · · Score: 0, Redundant

      It's a sad day when even mods don't RTFA (that's Read The Fine Article for all of you lovely people with mod points today :)

    10. Re:huh by Lifewish · · Score: 1

      I think themessenger was mainly being blamed for being a politically-incorrect asshole... I can sympathise with this point of view.

      --
      For the love of God, please learn to spell "ridiculous"!!!
    11. Re:huh by Anonymous Coward · · Score: 0
      I think he's a mature and well-adjusted young man (or woman), who just happens to be diligently searching for a way to hack into other people's computers for fun.
      </sarcasm>
    12. Re:huh by j-turkey · · Score: 5, Insightful
      There are certainly other ways to go about reporting bugs (not that Microsoft will listen to any of them), but blaming the messenger for pointing out that the castle wall is full of holes is a bit misdirected if you ask me.

      Maybe there's something that I'm misunderstanding here. You're suggesting that he's just a messenger -- nothing more? I completely disagree. This person posted an exploit. I'm not sure how it is where you're from, but from where I sit, posting an exploit is on an entirely different level from simply telling someone that their software is full of holes (including how and where).

      To use your analogy, rather than being a messenger telling the king that his castle walls are full of holes, this is a little more like designing a weapon to destroy your castle walls, and posting the plans in every neighboring town (which somehow manage to automatically build the weapon, provided you have the right tools). All the recipients have to do is tell the device to build itself, point, and fire.

      The point is that this guy was downright irresponsible and should be treated as such. Any sane king would have beheaded this person in a royal heartbeat.

      --

      -Turkey

    13. Re:huh by Anonymous Coward · · Score: 0

      the even scarier part is that a microsoft code auditor is not skilled enough to see that gaping hole.

      Yikes, this article on it's own made the IS department here start drafting a notice to the CTO as to the possible unstability and massive insecurity of microsoft software.

    14. Re:huh by CodeRx · · Score: 1

      This person (I'm not going to say "He" because hey, who knows?) obviously knows their stuff. I don't think they are necessarily immature - could just be a quirky sense of humor (not uncommon for geeks).

      I would guess this person is in their late teens or early twenties. If they were any older they would be making 6-figures working for eeye or @stake.

    15. Re:huh by Anonymous Coward · · Score: 0

      Believe me. This is the best 'open source kindaa' code-review that Microshaft has got, free of cost !

      My only target is those analyst who stick up for Microshaft and lick their feet, no matter what...

    16. Re:huh by m0rph3us0 · · Score: 3, Insightful

      It is only a root exploit if you browse as root. Who browses as root?

      Oh, yes, thats right Windows users.

      Ok carry on...

    17. Re:huh by iso · · Score: 0, Flamebait

      Completely off-topic, but "their" is not a singular pronoun. The proper singular pronoun, when sex is unknown, is "he." That's why I said "he."

    18. Re:huh by iamwahoo2 · · Score: 3, Insightful

      I think you are full of it. The poster has done a lot of folks a HUGE favor. If he had sat on this, and allowed MS to sit on this, possibly millions of unsuspecting IE users put their computers at risk, waiting for someone else with the knowledge to find this exploit who would use it in the wrong way. Thanks to the guys who disclosed this bug to the public, I will have the opportunity to tell my IE using freinds and family to make sure they are upgraded to IE6+ or are using Mozilla/Firefox/Opera, otherwise they are at risk every time that the view a picture.

    19. Re:huh by Deflagro · · Score: 1

      Actually if I were King, I would hire this guy as my military advisor and rule the coutry with an Iron fist! And call that country Microso..umm anyways.

      Maybe MS should take more pride in their work, I know they don't have to care, but they should

      --
      Der Tod ist der einzige Weg hier raus!
    20. Re:huh by tverbeek · · Score: 5, Funny
      a well-seasoned older programmer who has the social skills of a 13 year old?

      You say that as if it were unusual. ;)

      --
      http://alternatives.rzero.com/
    21. Re:huh by Anonymous Coward · · Score: 0

      Actually, AIDS really is pretty gay everywhere except Africa. The constant predictions of AIDS taking off into the non-IV drug using and non-hemophiliac heterosexual community have not come about.

    22. Re:huh by Anonymous Coward · · Score: 0

      Yeah, right! He broke the law and he should be concerned about PC?

      Hell, I don't break any laws deliberately, have no intention of exposing any root exploits and I don't give a damn about political correctness!

    23. Re:huh by Anonymous Coward · · Score: 1, Insightful

      To take your analogy further, imagine that you, as a messenger, are a citizen living withing the walls of the castle, and you know that an invading army is on its way.

      You know that there is a weakness in the walls, an exploit that could destroy the castle and inhabitants. You have been trying to convince people of this, but the king insists that there is nothing to worry about.

      To prove your point, you create plans for how to take advantage of this exploit and place it in public places for all to read.

      A king who would have beheaded this individual would be a tyrant, doing nothing but obscuring his own incompetence as a leader.

      This is a more appropriate analogy.

    24. Re:huh by Anonymous Coward · · Score: 0

      And if some PC nut says you are sexist for using "he", just say, "Well that is the queen's English"

    25. Re:huh by B3ryllium · · Score: 2, Insightful

      "their" is gaining popularity in the common vernacular as a way to create genderless sentences without having to resort to stupid "He/She" constructs. It may not be correct now, but if it gains more acceptance, it could be considered correct at some time in the future.

    26. Re:huh by Anonymous Coward · · Score: 2, Insightful

      Ummm, it's just a figure of speech, just like "I Jewed him down on the cost" and such. People already use the term "gay" to refer to things unpleasant. Sorry, boys, but you lost your term, just like you lost "queer". Time to make up a new one.

    27. Re:huh by Anonymous Coward · · Score: 0

      I found that he had enough stupidity to check it out then enough courage to post his findings (or brag about his findings), to make me read the article.

      But when I read that subject line I was seriously appalled. I hope that mainstream people lead to that article (by google news, slashdot and the like) do not think that all OSS (aka hackers to them) members are that crude.

    28. Re:huh by SloppyElvis · · Score: 5, Insightful

      It isn't all that difficult to narrow the search when looking for exploits like this. Its surprising (or maybe it isn't) that M$ never looked for them. At our shop, its common practice to detect dangerous code.

      Just search for all stack arrays in the source...

      $ egrep "\[[:digit:]+\]" ...

      ...then inspect the code for ways to read/write past the bounds. That narrows the search field quite a bit (ok, you'd miss arrays defined with #define symbols, but you'd catch the sloppy ones, which is what you want in the first place).

      Combine a search as above with one for calls to strcpy(), strcmp(), sprintf(), [or any other C runtime/misc. function that fails to check input], and you have an even smaller lump of code to inspect.

      So, the 13 year old wouldn't need extensive knowledge, just what you could glean from reading an article or two on buffer overflows. Still, I'd bet its a seasoned socially backward individual.

      Anyway, good question to ponder.

    29. Re:huh by acidrain69 · · Score: 1

      Does it really matter?

      There are plenty of people on /. that will minimize security risks and breaches by assigning them to "script kiddies". Yes, a script kiddy doens't have the knowledge and experience that a true classic hacker has, but they have the willingness, and it is ignorance to brush them aside for their youth, just as it is ignorance to put them on a pedestal like some hollywood movie, where everyone is astounded by some genius youth, because they themselves are clueless. Every threat should be based on the nature of that threat. Age has nothing to do with it. The author is neither ridiculously knowledgeable or well seasoned. The social skills are definately lacking though.

      How did they come across it so quickly? How do most buffer overflows occur? It can't be that difficult to search for these things. I'm sure with a little bit of effort, someone can design a lexical scanner to look for cases where an overflow can be executed. Keep track of data types on a symbols list, and look at the test cases. Then it is just a matter of scanning the data structures to figure out how to exploit it.

      --
      -- Having a Creationist Museum is like having an Atheist place of worship
    30. Re:huh by BlackCobra43 · · Score: 1

      Not true. Posting it on the Internet is more aking to posting in in towns ALL OVER THE WORLD, *including* the enemy town. You can NOT tell me that only goodwilled Windows users are going to read that.

      What you mention would be more akin to sending a bug report to MS, which is entirely reasonable.

      --
      I never spellcheck and I freely admit it. Save your karma for more worthwhile "lol erorrs" replies
    31. Re:huh by Gabriele+Capone · · Score: 1

      s/SecurityTracker/Full-Disclosure/

    32. Re:huh by Anonymous Coward · · Score: 1, Interesting
      The point is that this guy was downright irresponsible and should be treated as such.


      Both parties are irresponsible. Microsoft is notorious for doing nothing about security holes which are pointed out to them. Their inaction leads to people bypassing Microsoft altogether and just posting exploits in an attempt to force the matter. DOJ is supposed to go after Microsoft when they sit on their ass instead of fixing security holes, but we've all seen how well that has worked out.


      The "good citizen" thing to do would be to contact Microsoft, inform them of the security hole, the sample exploit and a patch. But, since this is taken from illegally obtained source code I doubt the author wants to risk it. In the end, this is just the result of Microsoft treating security problems as PR problems.

      My bet is that if they do anything at all about this, Microsoft will simply bitch. As is typical with Microsoft, a security hole is just another PR issue -- in this case an opporunity to spread Open Source FUD. It will still take Microsoft forever to patch this, despite having exploit code, identification of the hole and an obvious means to correct the problem.

    33. Re:huh by Anonymous Coward · · Score: 0

      Try telling that to my college english teacher.

      CodeRx (posting anon as we're way offtopic here).

    34. Re:huh by Beavis! · · Score: 1

      But how else do you force an ignorant and uncaring royal to secure his castle? Just tell him and you're likely to get a "Thanks. It's good that we know that, now let's assess how much of a threat it really is and if it doesn't appear to be one, we'll sit on it while we do other more profitable things" response. Sorry, but you've got to force people's hands on things like this. Personally, I'm all for full disclosure because it results in safer environments when the pressure is on. Where is the impetus to actually fix a problem when it's not a problem at the moment? Even more to the point, if fixing that problem is going to cost money, it's rare that most organizations (royalty or software companies) want to put money into something that they feel isn't immediately or visibly beneficial. I had an idiot boss once who didn't "get" the concept of a server. We had a Windows NT domain controller sitting in a closet as a PDC. It also handled DHCP, some file shares, WINS and DNS. We had a financial package that needed to run on a box that was up 24x7. At this point in time, it was running on the business manager's PC. If he was out, I would get a call from one of his lackeys who couldn't connect. I'd have to go up to his office, turn the machine on and make sure the service was started. I suggested to my boss that we get a server and put the server end of the application on it. His response, "What about the server downstairs?! It's not actually DOING ANYTHING....!" I almost tore my hair out. I explained that it WAS doing something and I could easily prove it by shutting it down before I went home. He ACTUALLY took me up on the offer. In the end, even though he realized that we couldn't use the PDC (a paltry Pentium 90 with 24 megs of RAM) he balked at the cost of a new server and instead chose to go with a new powerful workstation. He hated the idea of a box in a closet that "no one uses". If bosses think like this, then it's not a stretch to think that kings and software company CEOs also think the same way.

      --
      I try to be fu
    35. Re:huh by poot_rootbeer · · Score: 4, Funny

      Who browses as root? Oh, yes, thats right Windows users.

      I'm a safety-conscious Windows user! I never login as "root"! I just use the "Administrator" account instead!

    36. Re:huh by Anonymous Coward · · Score: 0

      Better get your updated version of the OED.

      Their is singular

    37. Re:huh by aberant · · Score: 1

      i would completely agree with the parent post if it were not for the fact that this is almost a textbook example of buffer overflow code. It's like mocrosoft copied it from some explot book to begin with, renamed it, and plugged it into windows.

    38. Re:huh by tsmithnj · · Score: 1

      Your example assumes the developers use Unix.

      Duh.....

    39. Re:huh by JustKidding · · Score: 1
      This guy did not provide an exploit. The file he attached would just crash IE, not execute code. He only showed how to overwrite EIP.

      To actually execute code, one would have to get the code in memory (not very hard, just recalculate the offset variable and stuff the code in the pixel map of the bitmap), but you'd also have to figure out where in the memory this code would be placed, in order to jump to the right place. Even though this is possible, and not very hard (anyone with some knowledge of assembly programming could probably do it. I'm fairly sure I could do it, given a day or so), it's nearly impossible for your average 15-year old script kiddie to do so.

      However, I do agree that he should have notified Microsoft and given them, say 5 days to come up with a patch. I mean, come on, the patch is like 15 keystrokes...

    40. Re:huh by Anonymous Coward · · Score: 0

      Which is exactly why it must be quelled immediately.

      Nip it! Nip it in the bud!

    41. Re:huh by sasami · · Score: 1

      "their" is gaining popularity... [i]t may not be correct now, but if it gains more acceptance, it could be considered correct at some time in the future.

      Not to mention that it was also considered correct at some time in the past.

      --
      Dum de dum.

      --
      Freedom is not the license to do what we like, it is the power to do what we ought.
    42. Re:huh by Anonymous Coward · · Score: 0

      Are you aware of the difference between telling someone how to do something, good or bad, vs. actually doing it?

    43. Re:huh by j-turkey · · Score: 4, Insightful
      I think you are full of it. The poster has done a lot of folks a HUGE favor. If he had sat on this, and allowed MS to sit on this, possibly millions of unsuspecting IE users put their computers at risk, waiting for someone else with the knowledge to find this exploit who would use it in the wrong way.

      I think you might have your terminology backwards. Posting the vulnerability is a favor to people. Posting an exploit is a different story altogether. Since you have a hard time differentiating, let me try to help you out:

      Vulnerability: "Hey, look -- I've found this hole in IE. Here it is, fix it. Everyone else -- this software sucks. Use something else."

      Exploit: "Hey, everyone (script kiddies included) -- here's some code that I put together that exploits vulnerable boxes. You don't have to know a damn thing to root a vulnerable box. You can use this for anything, spamming, DDoS attacks, mining for credit card numbers -- it doesn't matter -- crack away, oh 31337 ones."

      Now can you tell me which is more constructive? The exploit or vulnerability. Now rememeber that nobody finds an exploit -- they're all written. Vulnerabilities are found. I completely agree that vulnerabilities should be made public -- but as far as exploits -- you're dead wrong.

      Now, if you didn't have you terminology backwards, your logic is just irresponsible. How is an exploit any more helpful than a vulnerability report to bugtraq? How could it possibly benefit anyone other than the script kiddies who will eventually get their hands on this code? People need another exploit in the wild like they need another hole in the head. You will still have an opporitunity to tell your friends and family about your disscovery -- only you'll have time to tell them to update their browser...not that they've probably been rooted.

      PS -- next time, if you're less confrontational in your replies -- you will likely receive more friendly responses...ass.

      --

      -Turkey

    44. Re:huh by Anonymous Coward · · Score: 0

      No. The only gambit for not getting modded down is if you had said...

      Although I will certainly be modded down for saying this, it's a sad day when even mods don't RTFA.

    45. Re:huh by gnu-generation-one · · Score: 1

      "I will have the opportunity to tell my IE using freinds and family to make sure they are upgraded to IE6+ or are using Mozilla/Firefox/Opera, otherwise they are at risk every time that the view a picture."

      Or tell Privoxy to block bitmap pictures... who uses them on the web except by mistake?

      Yes I know it's a hack and not a real fix, but we already know that Microsoft products aren't safe without a linux machine to protect them, whether it be firewall or proxy or load-balancer [microsoft.com] or whatever...

    46. Re:huh by psavo · · Score: 1

      Yup. Not talking about that the only reported Windows holes are remote. Nobody is counting local ones as there's just too many of them.

      --
      fucktard is a tenderhearted description
    47. Re:huh by minus_273 · · Score: 0

      dude this is america, you cant sure him you cant stop him. its called freedom of speech. live with it

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
    48. Re:huh by j-turkey · · Score: 1
      This guy did not provide an exploit. The file he attached would just crash IE, not execute code. He only showed how to overwrite EIP.

      Yeah -- I noticed that in the snippet I read. This tends to help his "case" -- however, this is not a court of law, it's a court of public opinion. I believe that he could have just submitted a bug report to the variety of places where these can be made, and not written any code to help script kiddies along.

      Notifying MS would be nice too -- but I think we're getting ahead of ourselves. There's three levels of bastard (or lack thereof) to work with here:

      1. Notify Microsoft and give them x amount of time before you go public
      2. Just post the vulnerability -- watch 'em scramble for a fix
      3. Just post an exploit -- watch 'em squirm.

      This writer is on "level 3" (or maybe the grey area between levels 2 and 3). Sure, giving Microsoft some time would have been a nice thing to do, but justthe same, I'd take a straight vulnerability release over any code that will give script kiddies a leg up.

      cheers!
      --

      -Turkey

    49. Re:huh by j-turkey · · Score: 1
      Sorry, but you've got to force people's hands on things like this.

      Forcing someone's hand would be to release vulnerabilities without any warning. Releasing an exploit (or even the relevant part) is just being a monkeyboy. The only people an exploit in the wild helps are script kiddies.

      As far as your boss goes -- sorry. However, understand that just because your boss doesn't have any clue doesn't mean that all bosses don't. Mine knows just enough to respect my expertise -- that I keep her systems and network running at the lowest possible cost (within reason). Some executives who run software companies are smarter than others. Believe it or not, the folks at the top of the largest software company in the world know a thing or two about the business (I'd hope so, otherwise their shareholders are assholes for not firing them), and really do take security seriously. Things at Microsoft tend to run like molasses on a number of different levels. Furthermore, there are so many holes in their software that these things likely need to be triaged -- so an IE5 vulnerability might take a back seat to, say, a hole in the TCP stack that makes all network applications vulnerable. In any case, yah...I sorta do think that it's a stretch to take your single bad experience with your boss and apply it to all upper management everywhere...such thinking has led to very Bad Things throughout history.

      --

      -Turkey

    50. Re:huh by Inuchance · · Score: 1

      Better yet, his email address is on there, let's start signing him up for some mailing lists.

    51. Re:huh by Chris+Burke · · Score: 1

      He could have been using Cygwin, which I personally love.

      "Cygwin: Making Windows barely tolerable since whenever they started doing that."

      Okay, maybe I'll stay out of marketing.

      --

      The enemies of Democracy are
    52. Re:huh by Daniel+Phillips · · Score: 0, Flamebait

      That was interesting to read. It made me wonder who the people are who come up with these exploits. This person is obviously very immature, but also very knowlegable about programming to spot something so quickly in so much code. The question is, is this a ridiculously knowledgable 13 year old, or a well-seasoned older programmer who has the social skills of a 13 year old?

      Actually, I wonder who you are, somebody whining about immature programmers to avoid the uncomfortable thought that their Windows system is full of technical flaws, and that the company who is supposed to fix them is incapable or unwilling to do it.

      --
      Have you got your LWN subscription yet?
    53. Re:huh by zoloto · · Score: 1

      I don't know about you but on my linux box I changed root to Administrator (caps included)

      Pretty handy and sneaky. I love it when my brother over our lan tried to brute force my "root" password on the linux box

      you should try it.
      www.linuxfromscratch.org

      kick ass

    54. Re:huh by Anonymous Coward · · Score: 0

      You forgot "level 4" and "level 5":

      4. Make a nasty worm and set it loose upon the world as a zero day exploit.
      5. Keep the knowledge to yourself, and use it to own other people's computers and data for your own profit and amusement.

      In sum, this guy could have acted *way* more like a bastard than he did.

    55. Re:huh by iamwahoo2 · · Score: 1
      Since the guy/girl sent the report to security focus I do not think his intentions were to hand it out to script kiddies.

      Maybe you have an issue with the person for including a small sample displaying how simple it was to create an exploit but I think you are being a tad harsh since the author could have done worse things with this knowledge.

    56. Re:huh by j-turkey · · Score: 1
      In sum, this guy could have acted *way* more like a bastard than he did.

      LOL. For sure, he totally could have acted way more out. I wasn't going all the way up the bastard there...just to his level.

      --

      -Turkey

    57. Re:huh by LarsG · · Score: 3, Insightful

      Posting the vulnerability is a favor to people. Posting an exploit is a different story altogether. Since you have a hard time differentiating, let me try to help you out:

      What are you talking about? He posted a vulnerability and a proof of concept BMP that shows that the stack is overwritten. It doesn't do anything except crash IE5.0.

      If he had made a BMP that contained functional shell-code or similar nastiness ready to be used by script-kiddies, I'd agree with you.

      PS -- next time, if you're less confrontational in your replies -- you will likely receive more friendly responses...ass.

      It also helps to know what you're talking about before going ballistic.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    58. Re:huh by Anonymous Coward · · Score: 1, Insightful

      I too agree with you... it's much better to just report the vulnerability (and possibly provide a fix or atleast a temporary workaround), though there is one BIG problem:

      Some vendors (like Microsoft) doesn't acknowledge a vulnerability until there is an exploit released for it.... This has been proven over and over again.

      Conclusion: Proof of concept exploits aren't always a bad idea. //fatal

    59. Re:huh by myowntrueself · · Score: 1

      Well I got this in an email on 'Full Disclosure' and it came complete with html and a bitmap; in other words, with the POC exploit.

      --
      In the free world the media isn't government run; the government is media run.
    60. Re:huh by stmfreak · · Score: 1
      Maybe there's something that I'm misunderstanding here. You're suggesting that he's just a messenger -- nothing more? I completely disagree. This person posted an exploit. I'm not sure how it is where you're from, but from where I sit, posting an exploit is on an entirely different level from simply telling someone that their software is full of holes (including how and where).


      Where I'm from, many bugs reported by the test group are ignored if you cannot rub the reviewer's nose in the pile of stink that the bug could create. The passing sentiment that results in a WONTFIX or a POSTPONE to later releases tends to be coupled with a healthy misunderstanding of the risk and impact that such bugs can cause.

      Filing such an exploit demonstrating how easily a customer might encounter such a bug and what sort of damage it might cause is the ONLY way to guarantee a bug gets fixed.

      So yea, don't blame the messenger, unless they actually wrote a self-propagating virus and called that the message. Posting an exploit is no different that mentioning that guns allow one to exploit bank security and steal cash. There is a huge difference between informative and criminal.
      --
      These opinions guaranteed or your money back.
    61. Re:huh by chrootstrap · · Score: 1

      Oh come on. He was giving an example of how crappy the Windows source was. He saw a vulnerability, tested it, and released code to test it. There was no "payload", no obvious malicious intent; it was an example. We've seen that kind of thing in free software all the time. If he was really such an ass he wouldn't have announced the discovery out of his clique on IRC, etc.

      --
      Hacking articles at http://www.geocities.com/chroo
    62. Re:huh by Anonymous Coward · · Score: 0

      Anyway, I just read your post, and decided that you're GAYER THAN MICROSOFT.

    63. Re:huh by LarsG · · Score: 1

      1. Notify Microsoft and give them x amount of time before you go public
      2. Just post the vulnerability -- watch 'em scramble for a fix
      3. Just post an exploit -- watch 'em squirm.

      This writer is on "level 3" (or maybe the grey area between levels 2 and 3).


      No. He is on level 2. He made information about the vulnerability public, he did not provide a ready-to-run exploit that can be used by script kiddies.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    64. Re:huh by Anonymous Coward · · Score: 0

      Better yet, his email address is on there, let's start signing him up for some mailing lists.

      Just some friendly advice.. when you post suggesting people should bomb some random guy's email, don't sign it with you're own address.

    65. Re:huh by Russ+Nelson · · Score: 1

      Microsoft has a history of ignoring vulnerabilities that don't have published exploits. "Oh, that's just theoretically a problem. Nobody has actually broken into a server that way."

      Note that the author has not published an exploit usable by a script kiddie. Substantial programming (actual coding!) is needed to turn this proof of vulnerability into an exploit.
      -russ

      --
      Don't piss off The Angry Economist
    66. Re:huh by Hooded+One · · Score: 1

      Nobody is disputing his right to speak freely. However, everybody *else* is just as free to call him an idiot. Freedom of speach works both ways.

    67. Re:huh by Anonymous Coward · · Score: 0

      I never log in as Administrator, way to dangerous!!
      But I have moved my account to the administrator group so that I can install programs etc. ;-)

      P.

    68. Re:huh by wannasleep · · Score: 1

      He (possibly) broke the law because some corrupted politicians have given in to lobbies and declared that saying the truth (about security) may be a crime. On that point, he depends in which country he is in whether he has broken the law or not (although I would guess he is in the US)

      I am definitely not endorsing the comment, but politically correctness is just a way of hiding the guilty feeling of being racist/sexist/etc.etc. by describing your feelings in a nicer way.

    69. Re:huh by Anonymous Coward · · Score: 0

      He's a random hacker.

      Why the hell would you expect him to be politically correct?

      But he must be 30+, anyone younger wouldn't remember when HIV was GRID (Gay-Related Immune Disease or something...)

    70. Re:huh by wannasleep · · Score: 2, Insightful

      well, in this case there is not much difference between posting an exploit and just telling where the hole is. Just check this article:
      - somebody has told us how the code works
      - somebody else has posted a link to a site that explains how to make a buffer overflow exploit
      - yet another person has told us how bitmaps are organized
      The most important part is still missing: write the code that has to be executed.
      If you want to exploit the bug, all you need to do is to figure out the bitmap and read this article, no matter if the exploit has been posted or not.

    71. Re:huh by toddestan · · Score: 1

      So, did you recreate the root account as a regular user with no privileges and an impossibly long password?

    72. Re:huh by minus_273 · · Score: 1

      i was replying to the parent post which said someone should sue him

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
    73. Re:huh by Anonymous Coward · · Score: 0

      which is why we really don't pay much attention to kings anymore...certainly stopped lots of beheading and all that. I prefer a free press, don't you?

    74. Re:huh by zoloto · · Score: 1

      I did, it kicks butt!

    75. Re:huh by fermion · · Score: 1
      Finding these things are not hard if you know how to look for them. User input has to put into a variable. If the variable is not immidiately sanitized, then searching for the use of the variable will likely lead to a buffer overflow. Even if the variable is sanitized, perhpas it is improperly used elsewhere.

      From the trouble that MS has fixing these bugs, it appears that they routinely treat foriegn data as trustworthy, and put data and control functions on the same data lines. Both went out of style a long time ago, and both are unacceptable.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    76. Re:huh by Anonymous Coward · · Score: 0

      I'm 25 and I've heard several people use the phrase "as gay as AIDS" at the University I attend. I guess that's close enough to 30, but there are obviously 18 year-olds here being exposed to such a phrase ;)

    77. Re:huh by Anonymous Coward · · Score: 0

      What a stupid thing to say.

      It sounds like you are one of those immature programmers yourself, but on the anti-MS side (which is even more immature).

  3. See! by Anonymous Coward · · Score: 4, Funny

    More proof that code who's source is open is less secure!

    (trigger-fingered mods : thats a joke)

    1. Re:See! by Lumpy · · Score: 4, Funny

      Nahh...

      The virus writer used the links to the SECURITY_HOLE refrences in holes.bas module from the VB.NET code that IE is written in.

      --
      Do not look at laser with remaining good eye.
    2. Re:See! by gnu-generation-one · · Score: 1

      "More proof that code who's source is open is less secure!"

      Surely it's now more secure? The bug has been found. As soon as it's patched there'll be one less bug than there was yesterday.

      Assuming a patch, assuming people download it, assuming IE5 is still supported, assuming IE users aren't idiots, assuming air transport of pigs...

    3. Re:See! by Herkum01 · · Score: 1

      Reminds me of the idea of self-graded tests in school.

      MS: Yeap! Got another 100, give me that A++!

      Teacher: Are you sure? This the 5th test that you have gotten 100 on, but you keep failing all the quizes you take in class.

      MS: I study really hard for the tests but I don't study for the quizzes. A++ please!

      Teacher: Well lets take a look at it first...

      MS: What!? You don't trust me! I am insulted that you believe that the answers for my test are less than perfect!

      Teacher: That's right lets take a look here... Good god you missed that!

      MS: What?! Let me see that! *rub,rub,rub*, there it is fixed give me a 100!

      Teacher: That is not the way it works, give me back that test... You missed these three too!

      MS: Wait, Wait I think that I made a typo there, let me fix it...

      Teacher: Did you get anything right? You even mispelled your name!

      MS: Help, Help I am being oppressed!

    4. Re:See! by dasmegabyte · · Score: 1

      Whoa, there, asshole.

      If IE had been written in VB.NET, there'd be no exploit.

      1) By default, VB.NET performs automatic bounds checking. A negative offset would be caught before it was processed and would throw an exception.

      2) VB is also an exception handling language, so an error like this would exit the function, not reset the processor.

      3) There's already a set of BMP handling routines in the .NET framework, so you wouldn't have to write your own.

      --
      Hey freaks: now you're ju
    5. Re:See! by Anonymous Coward · · Score: 0

      thanks for your insight fuckwad.

      nice to see your repulsive personality is still raging.

    6. Re:See! by dasmegabyte · · Score: 1

      Hey, that cockknocker was besmirching a virgin programming language with rumors of her lascivious mother! As a cavalier and Microsoft apologist, I had to set him straight.

      --
      Hey freaks: now you're ju
  4. You thought Microsoft were tardy with by irn_bru · · Score: 2, Insightful

    bug-fixes and patches???? When the full force of this hits, you ain't seen nothing yet!

    1. Re:You thought Microsoft were tardy with by LostCluster · · Score: 3, Informative

      There apparently is already a fix for this one installed on many machines. It's called IE6.

    2. Re:You thought Microsoft were tardy with by lacrymology.com · · Score: 4, Funny

      "It's called IE6"

      Weird... I would have sworn that it was called Windows XP.
      -m

      --

      #
      # Modus Ponens
      #
    3. Re:You thought Microsoft were tardy with by cgranade · · Score: 5, Funny

      And here I was thinking it was called Mozilla.

      --

      #define DRM chmod 000

    4. Re:You thought Microsoft were tardy with by Lifewish · · Score: 5, Funny

      Mine's called "Linux". Seems to fix a whole host of problems.

      --
      For the love of God, please learn to spell "ridiculous"!!!
    5. Re:You thought Microsoft were tardy with by justMichael · · Score: 4, Interesting

      According to my logs 20 - 30%* of the people browsing with IE are still using 5.x.

      I know, UAs get faked all the time...

      * Depends on which site you look at.

    6. Re:You thought Microsoft were tardy with by Anonymous Coward · · Score: 0

      That's a very good point. Microsoft apparently already found the problem and had it fixed. Open source software isn't free from problems to begin with, it's just that with so many people working on it, the problems get resolved. For the end user, though, that means frequent updates. I think that for the majority of Microsoft users, eg. grandmas, kids, etc, who *don't* update their programs and everything every other day, having the source closed is a more secure option.

    7. Re:You thought Microsoft were tardy with by RESPAWN · · Score: 1

      Back when I was doing some contract work, one of my clients had a particular web-based application that required IE 5 SP2. It apparently didn't yet work correctly with IE6. Well, that was fine until MS mysteriously pulled support and removed the download files for IE5 SP2. It also kind of made you wonder what was so wrong with SP2 that they removed it like that without warning. (Or maybe they did give warning? I didn't know about it ahead of time either way, and IE5 without SP2 was still available making me wonder what was so bad about SP2...)

      Although I guess I shouldn't criticize. I just noticed last week that my laptop was running IE 4. Uh, and Windows 95... becuase it doesn't meet the minimum specs for 98...

      --

      If Murphy's Law can go wrong, it will.

    8. Re:You thought Microsoft were tardy with by FooAtWFU · · Score: 1

      No, they changed the name to Phoenix^H^H^H^H^H^H^HFirebird^H^H^H^HFox.

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    9. Re:You thought Microsoft were tardy with by Anonymous Coward · · Score: 0

      We have no way of telling how/what this "fix" is in IE6.

      Maybe they just changed the position you need to set.

      Unless you can see the code you dont know if the fix is actually a fix or just a fudge to satisfy the masses.

    10. Re:You thought Microsoft were tardy with by Anonymous Coward · · Score: 0

      This is a great idea! Next time some windows loser asks you to 'fix' his computer. You say, sure, I'm just gonna download and install this new patch. It's called linux...:-) Your computer will work much better from now on. Basically the same, just use that "K" or that little foot like the start button, and you're all set! ;=)

  5. so THATS why it was leaked by SlashDread · · Score: 5, Funny

    to fix it...

    "/Dread"

    1. Re:so THATS why it was leaked by Anonymous Coward · · Score: 2, Interesting

      exactly, it almost seems they intentionally released it so that the crackers can take a crack at finding new exploits so MS can fix them... they seem to understand the benefits of open source, but want to take advantage of it while still keeping things closed.

      or, one of the offshore programmers was stuck trying to fix a bug and posted a question to a board somewhere and put the code up so people could help fix it.

      nyeh.

    2. Re:so THATS why it was leaked by santos_douglas · · Score: 4, Interesting

      Think about it, the conspiracy theorists are right - the leak was on purpose. Call it Phantom Open Sourcing: pretend to leak your buggy source code, lots of programmers look it over and find all sorts of problems for free! All their developers continue working on new products and a few are assigned to make the new updates compliments of the leak. This will be hailed as the most brilliant management cost cutting strategy in history.

    3. Re:so THATS why it was leaked by Anonymous Coward · · Score: 0

      This looks more plausible.

    4. Re:so THATS why it was leaked by Anonymous Coward · · Score: 0


      Sure... why outsource development staff to India when you have a whole bunch of Open Source zealots who are willing to work at no charge? The GNU Manifesto hails again.

    5. Re:so THATS why it was leaked by Anonymous Coward · · Score: 0

      Most programmers won't bother.. It's the worm-writing people who will find the exploits. But we will find out about these holes when the worms start spreading. Not all these people are going to make the holes public.

    6. Re:so THATS why it was leaked by teklob · · Score: 1

      Also, you can easily steal the patches without legal issues because nobody is legally allowed to have the source
      *removes tinfoil hat*

    7. Re:so THATS why it was leaked by castrox · · Score: 1

      You forget to consider the businesses going DOWN because of exploits like these. How does that fit into your conspiracy theory?

      --
      Fight for your digital freedom, join the EFF *now*: http://www.eff.org/support/
    8. Re:so THATS why it was leaked by evbergen · · Score: 1

      Well, that too fits nicely into M$' agenda. "See how source availability is a security risk? OSS, full disclosure, they are threats to american business! Now, buy that safe, proprietary product from uncle Bill and you'll be a lot better."

      --
      All generalizations are false, including this one. (Mark Twain)
    9. Re:so THATS why it was leaked by castrox · · Score: 1

      Sorry but I don't buy that theory. It hurts more than it serves their agenda. Really.

      People are stupid, but I believe they'd be able to draw the conclusion that openness is a good thing since bugs will be corrected by the community.

      Oh well, thinking about it makes me a bit uncertain that people in general will actually "get it". You are technically right, but not practically (that's of course what I think) since, yeah, it'd be a too costly action, both image-wise and money-wise.

      It feels mostly like a conspiracy theory because the slashdot crows needs one.

      --
      Fight for your digital freedom, join the EFF *now*: http://www.eff.org/support/
  6. Is it good or bad by PhilippeT · · Score: 1, Interesting

    that the source was released? In a way it's good bugs will be identified. In another it's bad bugs will be exploited way faster.

    --
    A psychopath can't tell the difference between right and wrong. A sociopath knows the difference - he just doesn't care.
    1. Re:Is it good or bad by tomstdenis · · Score: 1, Insightful

      You sir are a moron. It's bad that the source got out. It means "clean house" implementations of similar technologies could fall to the MSFT whoredom.

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:Is it good or bad by Lifewish · · Score: 4, Insightful

      My feeling is that, in the context of preventing attacks, it's bad. With linux, discovery almost immediately leads to a fix cos it's the same volunteer community does the finding and the fixing, but Microsoft doesn't let the Bugtraqs of this world help. It's going to buckle under the strain of too many bugs at once.

      Of course, from the point of view of converting everyone to Linux, this can only be a good thing :)

      --
      For the love of God, please learn to spell "ridiculous"!!!
  7. Funny comment by the bugtraq submitter by Paladine97 · · Score: 0, Flamebait

    If you read the bugtraq article, notice how the poster claims:

    Anyway, I took a look, and decided that Microsoft is GAYER THAN AIDS.

    1. Re:Funny comment by the bugtraq submitter by Anonymous Coward · · Score: 5, Funny

      This means that the exploit is so obvious that even a 14 year old can figure it out.

    2. Re:Funny comment by the bugtraq submitter by scifience · · Score: 1

      Are you implying that 14 year olds are dumb? I'm 14, and take that comment quite personally. ;)

    3. Re:Funny comment by the bugtraq submitter by Anonymous Coward · · Score: 0

      I thought I was very smart when I was 14. I think I'm a lot smarter now (25) than I was when I was 14.

  8. The bitmap in question... by lacrymology.com · · Score: 4, Funny

    Of course the bitmap is of a penguin! More ammunition for the M$ FUD campaign.
    -m

    --

    #
    # Modus Ponens
    #
    1. Re:The bitmap in question... by p4ul13 · · Score: 4, Funny

      This seems to be what the BMP would look like.

      --
      Paul Lenhart writes words!
    2. Re:The bitmap in question... by n3k5 · · Score: 1

      An animated BMP? Rrrrright.

      --
      but what do i know, i'm just a model.
  9. What the fuck? by tomstdenis · · Score: 4, Funny

    What the fuck in a bitmap renderer could overflow and cause such problems?

    Fuck MSFT it's called bounds checking. e.g.

    1. load int from char array
    2. check int against sizeof(yourbuffer)
    3. reject if greater

    Not exactly a challenging task. I guess they're too busy adding in all that crapware to actually code at least one thing right.

    Tom

    --
    Someday, I'll have a real sig.
    1. Re:What the fuck? by millahtime · · Score: 4, Insightful

      "1. load int from char array
      2. check int against sizeof(yourbuffer)
      3. reject if greater

      Not exactly a challenging task


      It all goes to the quality of the coder. This is just plain bad code. I learned how to write something to check these kinds of things in middle school.

    2. Re:What the fuck? by vontrotsky · · Score: 5, Funny

      I think it went more like

      1. load int from char array
      2. check int against sizeof(yourbuffer)
      3. user=root if greater

    3. Re:What the fuck? by SlashDread · · Score: 5, Funny

      In the old days, when I was young system admin, it was called "Monkey Testing".

      It went something like this:
      You position yourself behind a functional input screen, and start hammering viciously and blindly. The latter is important, the more blind the better, it invokes he Holy Random God. Repeat for 5 minutes. You repeat this for each input screen.
      If the screen showed anything similar to "ERROR: OTHER INPUT EXPECTED" it passed.
      If it showed anything similar to "OK, 98zxc3v4^DD^C^Z NEW CUSTOMERS ADDED" or failed to read at all due to overly blinkeyness or so, it failed.

      I understand MS needs more monkeys.

      "/Dread"

    4. Re:What the fuck? by tomstdenis · · Score: 2, Funny

      char whatoverflow[3];

      scanf("%s", whatoverflow);

      ;-)

      --
      Someday, I'll have a real sig.
    5. Re:What the fuck? by DjReagan · · Score: 5, Informative

      That wouldn't work in this case. Overflowing a signed integer so that it wraps around to negative won't be picked up by checking if the value is greater. Using the correct datatype (unsigned int) would have been better.

      (in fact, looking at the code snipped in the vulnerability notification, they do check against Offset > size of buffer)

      --
      "When I grow up, I want to be a weirdo"
    6. Re:What the fuck? by PhilippeT · · Score: 1

      Stop posting snippets of my code you know its copywriter, trademarked and violates IP laws :)

      --
      A psychopath can't tell the difference between right and wrong. A sociopath knows the difference - he just doesn't care.
    7. Re:What the fuck? by david.given · · Score: 5, Interesting
      In the old days, when I was young system admin, it was called "Monkey Testing".

      This is moderated as funny... but it's true. You can even get software to automate the process. It just sends random keypresses and mouseclicks to the application under test, very very fast. You leave it running overnight. If you're application is still stable the next day, it passed.

      It's scary how many bugs a simple test like this can throw up...

    8. Re:What the fuck? by tomstdenis · · Score: 2, Funny

      MS optimized it [their innovative]

      1. Look at bitmap, get scared.
      2. user == root

      They also merged in a backdoor so the attacker wouldn't have to embed it in the bitmap

      3. open port 1234 as a rsh automatically logged in.

      Tom

      --
      Someday, I'll have a real sig.
    9. Re:What the fuck? by MoneyT · · Score: 5, Informative

      IIRC early Apple computers actualy had a memory location called "MonkeyLives" or something like that, which was used for a program they called the monkey. The monkey program randomly entered commands and clicks and such for as long as the program was running. The problem was, sometimes it would shutdown the computer (by executing a shutdown, not by crashing it) so they created a memory location that when shutdown was called, it first checked that location to see if the monkey program was running, and would cancel the shutdown if it was.

      --
      T Money
      World Domination with a plastic spoon since 1984
    10. Re:What the fuck? by Anonymous Coward · · Score: 0

      Kinda like the guy I write software for. I write it, compile it, and test it. It works. I give him the copy, he test it and fail. Why? Because when I test, I first and foremost just try to go through the events that SHOULD happen, whereas he seem to go through all other impossible events.

    11. Re:What the fuck? by tomstdenis · · Score: 1

      copyrighted? hehehe

      Probably violates the DMCA too right?

      Or as we say in Canada "le ACMD!"

      Tom

      --
      Someday, I'll have a real sig.
    12. Re:What the fuck? by xinn · · Score: 1

      If they get any more monkeys they may actually create, through the monkey/typewriter theory, something artful - do we really want that?

      --
      These are not the .sigs you are looking for. He can go about his business. Move along.
    13. Re:What the fuck? by Anonymous Coward · · Score: 0

      There are no more monkeys! That's the whole barrel!

    14. Re:What the fuck? by tomstdenis · · Score: 2, Interesting

      Which is why you load unsigned values. By "int" I meant "an integer".

      For example, from my LibTomCrypt a macro to load a variable length mp_int [mycrypt_pk.h INPUT_BIGNUM] logic works as follows

      1. inlen == sizeof input
      2. y = 0, current offset

      for all bignums
      1. if y + 4 > inlen return error
      2. load 32-bit unsigned into x, advance by 4
      3. if x+y > inlen return error
      4. load x byte mpint
      5. check if mpint loads correctly.

      [I'm in the middle of doing massive updates to my PK code though...;-)]

      But that's the jist of it. Really simple and since I use macros I only have to work out/code the logic once.

      Tom

      --
      Someday, I'll have a real sig.
    15. Re:What the fuck? by corbettw · · Score: 4, Funny

      By any chance, did the program come up with the entire works of Shakespear?

      --
      God invented whiskey so the Irish would not rule the world.
    16. Re:What the fuck? by AstroDrabb · · Score: 4, Funny
      I understand MS needs more monkeys.
      It appears they have their fair share already
      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    17. Re:What the fuck? by Walterk · · Score: 4, Funny

      I bet some MS exec misinterpreted it and used the monkeys for the coding, and not testing.

    18. Re:What the fuck? by Anonymous Coward · · Score: 0

      You position yourself behind a functional input screen, and start hammering viciously and blindly.

      Ah, so you hired Perl programmers.

    19. Re:What the fuck? by El · · Score: 1

      Using the correct datatype (unsigned int) would have been better. Too bad there are no unsigned ints in Java...

      --

      "Freedom means freedom for everybody" -- Dick Cheney

    20. Re:What the fuck? by prockcore · · Score: 5, Insightful


      Fuck MSFT it's called bounds checking. e.g.

      1. load int from char array
      2. check int against sizeof(yourbuffer)
      3. reject if greater


      AHahahaha, you know you just made the exact mistake MS did. You're using ints, not unsigned ints. Reject if greater does nothing if it's less than 0, which would still cause an overflow.

    21. Re:What the fuck? by roothog · · Score: 1

      For the academic slant: Fuzz testing of application reliability. It's amazing how many tools fail the random input test.

    22. Re:What the fuck? by Anonymous Coward · · Score: 0

      I understand MS needs more monkeys.

      So they can fix their code and write the complete works of shakespear at the same time?

    23. Re:What the fuck? by Delirium+Tremens · · Score: 1

      You don't have pointer either. So, who cares about buffer overflows?

    24. Re:What the fuck? by alannon · · Score: 3, Interesting

      There are also no exposed pointers in Java, thus no way to clobber the stack by writing to a negative array offset, as in this exploit. Reading or writing to a negative array offset in Java will result in a RuntimeException of some sort. Buffer overflows are also impossible in Java, since writing off the end of an array will result in a similar exception.

    25. Re:What the fuck? by 0x1337 · · Score: 1

      user == root?

      Well - i.e. '1' if the luser in question was root. So that starts a vicious cycle of I.E. getting scared of the bitmap. If the luser wasn't root - point 2 will point to point 0, which doesn't exist, invoking the General Protection Fault. yay.

      Ok I'll shut up now...

    26. Re:What the fuck? by tomstdenis · · Score: 1

      Which? French or English?

      I speaks them both ya dumb hockey hoser!

      --
      Someday, I'll have a real sig.
    27. Re:What the fuck? by Anonymous Coward · · Score: 0

      1. load int from char array
      2. check int against sizeof(yourbuffer)
      3. reject if greater

      Not exactly a challenging task.


      Nope. Except they did do that. I guess you didn't check the fuckin' code. The problem (which, if i take your post very literally) is the same one you made. They treated the size of the array as an int - but, it should've been an unsigned int - this lead, ultimately, to a bounds check failing if the 'int' read was 'negative'.

    28. Re:What the fuck? by Anonymous Coward · · Score: 0

      3. user=root if greater

      user=root??? Since when does Windows have a root user? I guess this algorithm must be used in Linux then.

    29. Re:What the fuck? by JoeBuck · · Score: 1

      My five-year old daughter is pretty good at breaking desktops.

    30. Re:What the fuck? by nacturation · · Score: 2, Informative

      You can read all the details on Monkey Lives here.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    31. Re:What the fuck? by spectecjr · · Score: 4, Insightful

      Fuck MSFT it's called bounds checking. e.g.

      1. load int from char array
      2. check int against sizeof(yourbuffer)
      3. reject if greater

      Not exactly a challenging task. I guess they're too busy adding in all that crapware to actually code at least one thing right.


      I guess you missed the original article, brainiac, but your code is flawed.

      "Reject if greater" will fail if int is negative.

      But hey, thanks for proving that you're as dumb as a box of rocks.

      --
      Coming soon - pyrogyra
    32. Re:What the fuck? by Trailer+Trash · · Score: 1

      We always referred to it as the "elbow test" since it is best done by using your elbows blindly on the keyboard. And, honestly, if you have a 1 year old kid around the house, all the better.

    33. Re:What the fuck? by wurp · · Score: 1

      Not to mention that you can fix it one time, for all your code, in C++ by creating and using a template wrapper for all arrays.

      template
      class Array
      {
      private:
      T* buff;
      public:
      Array()
      {
      buff = new T[size];
      }

      Array(T* b)
      {
      buff = b;
      }

      T& operator[](int index)
      {
      if( index = size ) {
      throw string("index out of bounds, size: ")+size+", index: "+index;
      }
      return buff[index];
      }

      const T& operator[](int index) const
      {
      if( index = size ) {
      throw string("index out of bounds, size: ")+size+", index: "+index;
      }
      return buff[index];
      }
      }

      That code's probably buggy as hell since it's the first C++ I've written in four years, but nonetheless, it's an easy problem to solve, and one that's been solved over and over again, if people would just use it. Just never ever create a raw buffer in your code and never ever do anything with a buffer someone passes to you without wrapping it first, and you eliminate the vast majority of buffer overflow bugs.

      Or you could just write your code in a language with built-in buffer overflow detection.

    34. Re:What the fuck? by ckaminski · · Score: 1

      it's too hard to do

      if ( 0 < buffer_location > max_buff_size ) { ...
      }

      this is SOP in any code I write when I'm not automagically using UINTs (interfacing with libc code)...

    35. Re:What the fuck? by Anonymous Coward · · Score: 0

      I understand MS needs more monkeys.

      Apes! Those damn dirty apes!


      Oops, no, they're GNU/Apes.

    36. Re:What the fuck? by tomstdenis · · Score: 1

      As you're the 9th person to point this out I'll reply once again. It was pseudo code. In my real code [re: LibTomCrypt for instance] I use unsigned types.

      Now stop thinking your leet shit by pointing out trivialities in PSEUDO-CODE and get a fucking life.

      Tom

      --
      Someday, I'll have a real sig.
    37. Re:What the fuck? by Prof.Phreak · · Score: 1

      Gives a new meaning to "There are viruses in image files!" :-)

      --

      "If anything can go wrong, it will." - Murphy

    38. Re:What the fuck? by ktulu1115 · · Score: 1

      Or even better, the source to Windows?

      --
      # fuser -v /dev/attention | grep work
      #
    39. Re:What the fuck? by MrHanky · · Score: 1

      I did that to Windows XP's login screen at a friend's house. It bluescreened and rebooted. I was very drunk at the time, so it's possible I hammered more randomly than XP expected. Or maybe it wasn't random at all, I don't remember. My point is, if MS did monkey test XP, they used the wrong monkey. You have to use a drunk monkey as well.

    40. Re:What the fuck? by ajna · · Score: 2, Interesting

      In fact I helped code part of this functionality when I interned at Palm, on the Pose project. There was already a Gremlins functionality (along with GremlinHordes, which were Gremlins with different seed conditions) that would send bits of Shakespeare to text entry boxes, click randomly (weighted for actual button locations) and generally wreak havoc for a predetermined number of events. What I helped add was a logging, playback-from-log and minimization routine that would find the minimal subset of the events that would crash the Palm app being tested at the time. Fun stuff, that was. Since Pose/Poser is open source, you can now see my handiwork in file EmMinimize.cpp (or was it EmMinimization.cpp?) in the source distribution. http://www.palmos.com/dev/tools/emulator/#source

    41. Re:What the fuck? by TALlama · · Score: 1
      --

      - The Amazina Llama

    42. Re:What the fuck? by MoneyT · · Score: 1

      Not to nitpick, but it's still a memory location:

      We kept our system flags in an area of very low memory reserved for the system globals,

      --
      T Money
      World Domination with a plastic spoon since 1984
    43. Re:What the fuck? by Russ+Nelson · · Score: 1

      My daughter found a bug in a program that had been used for many years. She was 1yo at the time, and was banging her hands on the keyboard ("Look, mom, I'm typing just like Daddy does!") and somehow crashed the Galahad word processor. Fortunately, I saw (mostly) what keys she had pressed, and was able to reproduce it.
      -russ

      --
      Don't piss off The Angry Economist
    44. Re:What the fuck? by 1010011010 · · Score: 1
      They could have used a signed int, but checked for both a minimum and maximum acceptable value.
      if (cbSkip > 1024)
      cbSkip = 1024;
      if (cbSkip < 0)
      cbSkip = 0;
      or even stuff the bounds check in a macro
      #define boundsCheck(x,min,max) ( (x)<(min)?(min):(x) ) > (max)?(max):( (x)<(min)?(min):(x) )

      int
      main(int argc, char **argv)
      {
      char buf[1024];
      int offset=2147483647,x=0;

      printf("Buffer size: %d\n\n", sizeof(buf));

      for (x=0; x<3; x++)
      printf("Offset: %d bounded offset: %d\n\n",
      offset+x, boundsCheck(offset+x,0,sizeof(buf)));

      };

      /* produces
      Buffer size: 1024

      Offset: 2147483647 bounded offset: 1024

      Offset: -2147483648 bounded offset: 0

      Offset: -2147483647 bounded offset: 0
      */
      ... there's probably a more efficient way to write it, it might not bounds-check the way you want (e.g., overflows are zeroed), and I'm certainly going out on a limb posting C code here on /., but there you go.

      Using the right datatype to begin with is better, of course.
      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    45. Re:What the fuck? by Anonymous Coward · · Score: 0

      Spanish. It's the new English!

    46. Re:What the fuck? by mindriot · · Score: 1
      1. load int from char array

      ...and you have failed already. What you should've done:

      1. load unsigned int from char array

    47. Re:What the fuck? by Anonymous Coward · · Score: 0

      Bet you're feeling very clever huh? Well, check this exploit. You'd be caught as well. The buggy code in question DOES in fact check whether the offset is bigger than the buffer. It does not check whether is is smaller than 0... yes, the offset is a SIGNED int. Oops.

    48. Re:What the fuck? by innocent_white_lamb · · Score: 1

      Because when I test, I first and foremost just try to go through the events that SHOULD happen, whereas he seem to go through all other impossible events.

      In my experience it is practically impossible for the same person who wrote a particular program to test it adequately. I can spend what I figure is a lot of time checking what I think is most trivial functionality in a program, then give it to a user and have him on the horn five minutes later telling me that he just got an error message.

      As you say, I think the reason is because the chap who writes the program knows what it's supposed to do, so to test it he goes through the program and says, "Yup, it does what it should." The end-user, though, says, "Am I supposed to push X or Y here?", presses Y, and blammo! Well, who the hell would press a Y there? Obviously, the end user.... Oops. I'll fix that and get it right back to you.

      --
      If you're a zombie and you know it, bite your friend!
    49. Re:What the fuck? by Anonymous Coward · · Score: 0

      The fact that it was signed rather than unsigned was key. So if you're going to correct this even in psuedocode, you need to make the distinction. Otherwise you really haven't corrected anything.

    50. Re:What the fuck? by tomstdenis · · Score: 1

      What was signed? I don't recall posting ISO C code here. I posted pseudo-code. In my pseudo-code language all "ints" are unsigned.

      There. Now I'm correct and you're wrong. Go fuck yourself.

      Tom

      --
      Someday, I'll have a real sig.
    51. Re:What the fuck? by bonch · · Score: 1

      Man, you clearly feel stupid for having your flawed code pointed out.

      Even pseudo-code should mention an unsigned integer.

      That fact that you keep using the word "fuck" in all your replies signifies that you have the social skills of a small reptile. Get out and experience life a little bit. There's more to it than posting flawed pseudo-code to a Microsoft article.

    52. Re:What the fuck? by k4_pacific · · Score: 1

      So that is why Java's so slow and won't link with my static libraries.

      --
      Unknown host pong.
    53. Re:What the fuck? by Anonymous Coward · · Score: 0


      Linus uses something similar, called crashme:
      http://linux.maruhn.com/sec/crashme.html

    54. Re:What the fuck? by alannon · · Score: 1
      So that is why Java's so slow and won't link with my static libraries.

      These days, the speed of code written in Java is generally equivalent to code written in C or C++. Most of the overhead in running Java comes in the form of excess memory usage. The CPU overhead of runtime compiling, bounds checking, garbage collection and other runtime services is about balanced with the performance increases that are made with the runtime optimizer.

      The AWT and Swing graphical toolkits that come with Java are pretty horrid, though, and are slow. The trend these days seems to be using IBM's SWT for implementing GUIs. My experience using programs written for SWT have been performance and responsiveness similar to a fully native program.

      I'm not sure what your gripe is about not being able to link your static libraries to Java, though. Java doesn't have a compile-time linker. All linking is done at class load time. If you have code written in C or C++, you're always welcome to use JNI (Java Native Interface) to call it.

      Of course, you're probably just trolling. IHBT, I guess.

    55. Re:What the fuck? by Anonymous Coward · · Score: 0

      Ahem - when is Java code perform at the same speed as native compiled C code? Java byte code
      is nothing more than P-code. It's still at least 30 to 50% slower than native code.

    56. Re:What the fuck? by Anonymous Coward · · Score: 0

      But hey, thanks for proving that you're as dumb as a box of rocks

      I think you meant 'a bag of hammers', didn't you?

    57. Re:What the fuck? by FredGray · · Score: 1
      Ahem - when is Java code perform at the same speed as native compiled C code? Java byte code is nothing more than P-code. It's still at least 30 to 50% slower than native code.

      It gets compiled to native code at runtime by the virtual machine. At that point, the VM has some context to work with, so it can often make better optimization decisions. On some numerical benchmarks and on some VMs, you will even see Java performing better than C. However, every VM has cases that it handles well and cases that it doesn't, so it's difficult to make blanket statements about relative performance.

    58. Re:What the fuck? by ocie · · Score: 1

      They obviously don't use their own tools. Last time I programmed in windows, some little paperclip came up and said "It looks ike you're writing a shell sort routine. Would you like me to add bounds checking?"

      --
      JET Program: see Japan, meet intere
    59. Re:What the fuck? by ocie · · Score: 1

      I think you meant 'a bag of hammers', didn't you?

      Skinner: Yes, it's a regional dialect.
      Chalmers: Uh-huh. What region?
      Skinner: Uh, upstate New York.
      Chalmers: Really. Well, I'm from Utica and I never heard anyone use
      the phrase, "steamed hams."
      Skinner: Oh, not in Utica, no; it's an Albany expression.

      --
      JET Program: see Japan, meet intere
    60. Re:What the fuck? by zhenlin · · Score: 1

      Might want to be careful with that.

      If 'yourbuffer' is in fact a pointer... sizeof(yourbuffer) returns 4.

      Most of the time, buffers are statically allocated on the stack, so sizeof(yourbuffer) works as expected.

      Just too bad that stack buffers are the easiest to exploit...

    61. Re:What the fuck? by Anonymous Coward · · Score: 0

      That is a retarded explanation. You are just looking for something to bitch about.

  10. well, the source is out there by WebMasterJoe · · Score: 5, Interesting

    Wouldn't it be interesting to see the patch come out later today, from an anonymous source!

    --
    I really hate signatures, but go to my website.
    1. Re:well, the source is out there by hawkestein · · Score: 2, Interesting

      How would you know whether or not to trust it? It's not like the patch could be released as source, is it? Not all of us have the code.

      --
      -- Will quantum computers run imaginary-time operating systems?
    2. Re:well, the source is out there by Thud457 · · Score: 3, Interesting

      It'd be more interesting if Microsoft accepted the sumbission of the patch!

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    3. Re:well, the source is out there by WebMasterJoe · · Score: 2, Interesting
      How would you know whether or not to trust it? It's not like the patch could be released as source, is it? Not all of us have the code.
      In the real world, this probably would not be the official patch. But MS would have to decide between using the rogue patch, or writing a patch independently of the publicly-available source. The latter choice means a known vulnerability with a known solution would be in the wild while the vendor looks in the other direction (theoretically) while writing its own patch.

      And then, if this sort of thing happens again in the future, we would want to find out if MS used the rogue patch and claimed to write their own independently. By then, the company will be the equivalent of today's SCO - not really releasing anything of value, but suing people for using some phantom bit of source code that they bought the rights to a few years before.
      --
      I really hate signatures, but go to my website.
    4. Re:well, the source is out there by gnu-generation-one · · Score: 2, Funny

      "Wouldn't it be interesting to see the patch come out later today, from an anonymous source!"

      Line 3: replace "int" with "unsigned int"

      Do I need to be anonymous for this to work?

    5. Re:well, the source is out there by MoogMan · · Score: 1

      Or even, maybe MS will bring out a patch earlier than normal, since they dont have to search for the offending source code :)

    6. Re:well, the source is out there by Reziac · · Score: 1

      Especially if the patch were GPL'd ;)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    7. Re:well, the source is out there by the_truk_stop · · Score: 1
      Wouldn't it be interesting to see the patch come out later today

      It just got released! Get yours today!

  11. And counting by millahtime · · Score: 5, Interesting

    So, what is this... like the 10,000 IE security hole reported in the last couple years. Why write another IE virus? Is there really any challenge left?

    1. Re:And counting by Rotting · · Score: 3, Insightful

      How many issues would be resolved by simply using an alternate browser (mozilla for example)? I know this would not fix all of the problems but I am sure it would help some.

    2. Re:And counting by Anonymous Coward · · Score: 0

      So, what is this... like the 10,000 IE security hole reported in the last couple years. Why write another IE virus? Is there really any challenge left?

      If you're thirteen, then yes.

    3. Re:And counting by RomikQ · · Score: 5, Insightful

      Even, for an IE hole, this is pretty severe - now worms just have to send html emails with an img tag that points to a specific bitmap and voila: anyone who uses an mshtml based email client(including webmail) and hasn't updated for a while gets infected just by opening the message.

      Sure, sooner or later hotmail will stop showing bmps in messages and issue a warning like "if you get a message, do not open it, but delete immediatly", but hey, I bet the amount of worm emails in my Junk mailbox will increase drastically in the next couple of weeks.

      --
      Join the elite! Post at score:2! Ghostwheel is online.
    4. Re:And counting by edalytical · · Score: 1

      If it was really about the challenge we would see Linux and Mac viruses.

      --
      Win a signed Stephen Carpenter ESP Guitar from the Deftones: http://def-tag.com/?r=0008781
    5. Re:And counting by Viadd · · Score: 2, Funny
      Sure, sooner or later hotmail will stop showing bmps in messages and issue a warning like "if you get a message, do not open it, but delete immediatly"

      According to the comp.basilisk faq about Basilisks (images that cause system crashes in wetware):
      10. Is it true that Microsoft uses basilisk booby-traps to protect Windows 2005 from disassembly and pirating?
      We could not possibly comment.
    6. Re:And counting by Anonymous Coward · · Score: 0

      Yahoo mail already has an option to not display images in email. It displays all the text/tables/formatting, etc. You can click the "Show HTML graphics" link to see the pictures.

  12. It may not of been a secret to everyone by Anonymous Coward · · Score: 5, Insightful

    Just to those that couldn't get access to the source code. Some people with access before may have known about this for a while. Not that we'll ever know.

    1. Re:It may not of been a secret to everyone by Anonymous Coward · · Score: 0

      We knew, but we weren't particularly fond of the idea of being sued.

  13. No Problem by Jedi1USA · · Score: 5, Funny

    Microsoft just needs to get a copy of the leaked code and look it over for potential exploits.

    Oh wait. :^)

    --
    My old sig was REALLY stoopid.
  14. I'll be first to say it by MicroBerto · · Score: 5, Interesting
    IF this is true, the release of the source is the nail in the coffin for Microsoft.

    An exploit this quick? There's going to be some serious happenings going on at Microsoft. Also look for another Longhorn delay sometime due to everything that is found out.

    I'm not sure what to think. I'm not happy that when I get back to work this summer, I'm going to spend way too much time fighting these problems/viruses and patching things up. I'm not happy businesses are losing money. I am, however, happy that Microsoft is forced to clean up their act even more, or they are going to lose market share.

    Open source isn't 'communistic' -- it's capitalistic. Why? It increases competition.

    We have an interesting 6 months ahead of us, folks.

    --
    Berto
    1. Re:I'll be first to say it by KingOfBLASH · · Score: 5, Insightful

      IF this is true, the release of the source is the nail in the coffin for Microsoft.

      Actually I think that, if Microsoft doesn't lose it's customer base to all the exploits found, it's going to make Microsoft stronger. Think about it, right now Microsoft is receiving the same kind of security review that makes OpenSource products so strong in the first place. Granted, it's coming at a very high cost, but their source code will have much fewer bugs when this is over.

    2. Re:I'll be first to say it by HardCase · · Score: 4, Insightful
      IF this is true, the release of the source is the nail in the coffin for Microsoft.


      Please...you might as well say that BSD is dead. Nobody is happy about all the ruckus that the whole affair is going to raise, but it's a little early to pronounce Microsoft dead.


      -h-

    3. Re:I'll be first to say it by jwthompson2 · · Score: 0

      Will they be able to keep the code base clean though or as they add new stuff will it just get all messy again?

      --
      Even if I knew that tomorrow the world would go to pieces, I would still plant my apple tree. -Martin Luther
    4. Re:I'll be first to say it by nairnr · · Score: 1
      Then again, this could be a subverse attempt to get the benifits of open source without going open source.

      Their QA cycle just got a lot quicker :-)

    5. Re:I'll be first to say it by GoofyBoy · · Score: 1

      Umm.. you aren't the first to say that this might be bad for MS. And there were lot more insightful/interesting comments on this exact issue before.

      >An exploit this quick?

      Its the first exploit reported. Black hats could have known lots of exploits a long time ago, they just don't report it.

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    6. Re:I'll be first to say it by Cereal+Box · · Score: 0, Flamebait

      An exploit this quick?

      Well yeah. If you think about it, I'm sure just about every Linux zealot on the planet is frantically analyzing the source to create an exploit for each and every hole they can find in an effort to prove just how inferior Windows is to Linux. I'm sure if a bunch of Windows zealots were working around the clock to create Linux exploits you'd see Linux exploits pop up with the same amount of frequency.

    7. Re:I'll be first to say it by bmwm3nut · · Score: 4, Insightful

      yes, but that's assuming that everyone who finds a simple exploit like this one actually reports it. i can imagine that there'd be a number of black hats that will find and use these kind of exploits and not tell anyone how they did it.

      but i am happy that this leak happened. it just shows that the code should be out for peer review from day one. security-by-obscurity is second only to security-by-telling-people-what-not-to-do. (e.g.: "don't open that door, there's valuable stuff in that room")

    8. Re:I'll be first to say it by lacrymology.com · · Score: 5, Funny

      "We have an interesting 6 months ahead of us, folks."

      I can see the headlines now;

      "New exploit found in IE5"
      "Yet another exploit found in IE5"
      "Exploit found in Minesweeper"
      "Expolit found in Notepad"
      "Yet another exploit found in Minesweeper"
      "Yet another exploit found in Notepad"
      "New exploit found in IE5"
      "God damn! Another exploit found in Minesweeper"
      .
      .
      .
      "Exploit found in taskbar"
      "Exploit found in Times New Roman"
      "Exploit found in bootstrap"
      "Exploit found in Wingdings"
      "Exploit found in ...."

      Sounds pretty redundant and boring to me. ;)

      -m

      --

      #
      # Modus Ponens
      #
    9. Re:I'll be first to say it by bshroyer · · Score: 1

      I'm sure if a bunch of Windows zealots were working around the clock to create Linux exploits
      except that they'd have some problems there, as there's not much of the GNU/Linux source written in Visual Basic, VBScript, or Dot Net :)

      you'd see Linux exploits pop up with the same amount of frequency
      Highly doubtful. Given the fact that there could very easily be two orders of magnitude MORE Windows "zealots" out there than Linux zealots, how do you explain that we see a handful (one hand) of Linux exploits each year, Vs. dozens (nay, hundreds) of exploits for Windows? The math just doesn't support your assertion.

      And do you think that this is the ONLY exploit we'll see out of the code leak this week? I'm putting my money on at least two more before the end of the weekend.

      --
      The cure for cancer is coming: Reovirus
    10. Re:I'll be first to say it by Phillup · · Score: 2, Insightful

      Not everyone that looks at this code is going to be nice enough to tell the "good guys" about the exploits.

      Instead, they will write and release exploits... leaving MS to find the particular code that is messed up.

      --

      --Phillip

      Can you say BIRTH TAX
    11. Re:I'll be first to say it by Boing · · Score: 1
      That is, except for the fact that they could theoretically just go on making the same mistakes again, closing off the source and doing everything apparently possible to ensure that security warnings go unheeded.

      I'll admit, though, that the publicity that will result from the many, many new viruses and exploits in the coming months will probably light a fire under Microsoft's behind to pay more than lip service to revamping their security practices.

    12. Re:I'll be first to say it by KingOfBLASH · · Score: 1

      Well they'll probably get the code base dirty again with typical MS exploits. But the point is that since they borrow code from OS to OS, Longhorn may inadvertantly be strengthened.

    13. Re:I'll be first to say it by Anonymous Coward · · Score: 5, Insightful

      Granted, it's coming at a very high cost, but their source code will have much fewer bugs when this is over.

      There is only one problem: the source code is ilegal.

      Most people who find and report bugs will probably never see this code, and if they do see it, they'll deny it. This means that most people looking at the source code for bugs are doing so for their own benefit.

      It'd be very naive to believe that these black hats will release information about the bugs they found. In the case of this IE5 bug we can say that the guy who found it is probably a young fellow looking for m4d pr0pz.

      IMO, this source leak is very bad for MS, for it will get the worst part of both, closed source and open source, worlds. In one hand, every bad guy out there can, and will, see the code, in the other hand every white hat is legally and ethically forbidden to look at the source.

      Unless MS is trying to pull an SCO, I can't imagine a worst scenario.

    14. Re:I'll be first to say it by MoneyT · · Score: 1

      The numbers game could simply be a matter of windows zealots being of a lower magnitude (those actualy capable of finding these exploits I mean) or also because perhaps they have other things to do with their time than run throught elinux code (like keeping windows from dying on them). I'm not defending MS here, but the grandparent does make a point about a lot of this speed probably has something to do with certian linux fan boys spending the last week or so going through this code and trying their damndest to make an exploit.

      --
      T Money
      World Domination with a plastic spoon since 1984
    15. Re:I'll be first to say it by micromoog · · Score: 1, Flamebait
      I'm sure if a bunch of Windows zealots were working around the clock to create Linux exploits you'd see Linux exploits pop up with the same amount of frequency.

      If this is true, why hasn't Microsoft put a bunch of people on this very task, to discredit Linux?

    16. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      You're a fucking idiot. Most Linux users DON'T GIVE A SHIT and don't even want to look at the code. If you haven't notice, it's been spreading on WINDOWS P2P SYSTEMS.

      Fucking smacktard. It's always about Linux users hating Microsoft. WE DON'T GIVE A SHIT! I've been a Linux user for years, and I've got no intention of peaking at a single line of code... I guess that's too late though, because fucking moro0ns like your are posting it on Slashdot.

      Asshat.

    17. Re:I'll be first to say it by Frizzle+Fry · · Score: 1
      Not everyone that looks at this code is going to be nice enough to tell the "good guys" about the exploits.

      Instead, they will write and release exploits...

      True. But the same is also true of linux, etc.
      --
      I'd rather be lucky than good.
    18. Re:I'll be first to say it by merdark · · Score: 1

      Open source isn't 'communistic' -- it's capitalistic. Why? It increases competition.

      Sure, and Russia increased competition with the US and other world powers. Yet the people who were doing all the work got very little, and the guys at the top got a lot. Contrasting this to open source, the open source programmers get mostly 0 income, yet Red Hat, get's a fair bit.

      I should also point out that Red Hat employs a very small percentage of open source programmers.

      We have an interesting 6 months ahead of us, folks.

      This leak will not make the next 6 months any more interesting than the last six months. You find security flaws in old microsoft products interesting? I personally find the next generation of software much much more interesting. And I'm not talking about open source cloning of existing levels of integration in other operating systems (this should have been done long ago).

    19. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      Why? It increases competition

      Funny I never thought that what software my competitors used in their office was what I was competing against. This makes all the difference now, I can finally stop offering all those non-computer related services to my clients knowing that if I change to open source I will beat the pants off them and get all their clients as well. Thanks for this information you must be one truly exceptional business analyst.

      Sure by switching to open source I will save money on software. Probably the same amount that my competitors will save when they switch too. Now where does this "open source" competition you mentioned come from? Most competition between businesses are not computer related.

    20. Re:I'll be first to say it by Anonymous Coward · · Score: 1, Insightful

      Where you mentioned,

      "Open source isn't 'communistic' -- it's capitalistic. Why? It increases competition.",

      it feels right to mention that in releasing this, the win9x hold-outs are going to be scrambling to purchase the latest-and-greatest Microsoft offerings (Operating systems and the hardware to support them), unless they have access to a Linux-geek/young computer tech who will tell them to relax and migrate their "data" to a cd-rom/dvd-rom and install Linux instead.

      Microsoft has wanted to see the win9x/win2k crowd go for a while now, this looks like a really rough way to do it (one stone, many birds).

    21. Re:I'll be first to say it by NatasRevol · · Score: 1

      It's called a bandwagon. It's been around here for a while. I think you need to hop on.

      --
      There are two types of people in the world: Those who crave closure
    22. Re:I'll be first to say it by JoeBuck · · Score: 1

      On the contrary: by making older Windows versions unusable, this release may force everyone to "upgrade" to XP, thus reducing Microsoft's costs.

    23. Re:I'll be first to say it by groomed · · Score: 0, Troll

      Microsoft is receiving the same kind of security review that makes OpenSource products so strong in the first place.

      Where is the proof of this alleged strength?

      All of the biggest exploits/worms on Windows can be explained by a combination of popularity and user unawareness. The fact that the source code is not available for public auditing might be a factor in mitigating these exploits, but from all available data, it seems to be a minor factor at best.

      How does the "open source is more secure" theory explain the excellent security record of closed source systems such as HPUX, AIX and Solaris when compared to (say) Linux? How does it account for the fact that shell.sourceforge.net, debian.org and savannah.gnu.org have all been hacked recently, whereas microsoft.com has never been known to be hacked?

      Sorry, I don't buy it. The position that open source leads to more secure software is simply untenable.

    24. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      "Open source isn't 'communistic' -- it's capitalistic. Why? It increases competition."

      No, you are wrong.

      Communism is about sharing resources and giving each person an equal opportunity in creating a good and happy life. Its about "From each according to his ability, to each according to his need". (just like open source).

      In communist russia, for example, (a country that actually was not communistic, however it was a country without capitalism so it works as an example of competition outside of capitalism), ballet dancers and scientists, ice-hockey players, etc, WAS competing, believe it or not..

      However, they did not compete over money or better living but rather prestige, reputation, (or national pride ;), etc.. What I mean with this is that competition and communism is not mutually exclusive (as long as the competition is not about material gain in some way, etc).

      However I do not believe that "capitalistic competition" is a necessity for innovation. Why do humans innovate? Well, I agree that today some people do it for money or competition. But most people do it because they are really intrested in that particular field of science, if someone else improves his invention - he is happy about it. Then he might try to improve the invention again, etc. You can call it competition if you like, but I would not compare it to the capitalistic style of "destructive competition", it is rather some form of natural cooperative competition. Or rather cooperation. If you cooperate with someone in doing something, you will always have some different ideas about something - and yes, that is competition per se, but on the whole it is cooperation.. Do also remember that different open source projects can freely lend code and/or ideas from each other. - which is one reason that open source is so successful - "one does not need to invent the weel (or license it ;) if it is already invented.."

      Many people say that Gnome and KDE is in competition. But what kind of competition is that?

      I think that both Gnome and KDE fill a sligtly different niche - and as long as there are people with different taste - they will always exist. In a typical captalist environment small niche products can seldom survive - leading to a "unification" of different products in the same niche; "its about customer expectations". In a capitalist environment company X wants to "win the entire market" preferably by eliminating its competitors in different ways, for example by making the "best" product that fits the most people, or by doing some kind of microsoft-style-vendor-lockin, etc. However company X would always be more happy if the other company did not exist - or if they wouldnt have made the latest innovation. Pfizer does not wish AstraZenica good luck with their new patent applications, or inventions/drugs, etc, etc.. They are NOT happy when the other party recieve the exclusive rights on some receptor in the brain, or whatever.. (patents is by the way an excelent example of "destructive competition").

      In the opensource world there is "cooperative competition", there is room for everyone. There can, for example, exist thousands of window managers, some big and popular ones and some really small, but the goal of KDE (or Gnome) will never be to "eliminate the others" or to "dominate the market". The competition is not a capitalistic competition - its a cooperative competition. Everyone is doing what they can do to make life better for everyone.. ..and how can you ever compare that to capitalism? :)

    25. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      Exploit found in solitaire, microsoft's flagship product.

    26. Re:I'll be first to say it by Ymiris · · Score: 1

      Coming from a man who works mainly with Windows admins, the word on the street is HAHAH windows source code leaked from a Linux box. Shows are secure Linux is.

      Don't kill the messenger, just passing on info

      --
      **It runs through my veins like radioactive rubber pants! Do not deny my veins!**
    27. Re:I'll be first to say it by Inuchance · · Score: 1

      Well, the problem is: If they're not using Windows, what WILL they use? I don't even want to THINK about having to help some of the people I know with Linux...

      "Okay, now type in 'cd /usr/src/linux' so that you can compile your kernel."
      "What does cd do?"
      "It changes directories."
      "I don't have directories, all I have are these folders. And can't I just use the source code without compiling it?"

    28. Re:I'll be first to say it by EnderWiggin99 · · Score: 1

      If I had mod points, I'd mod you a troll!

    29. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      Actually, it *could* be that M$ will use this as an excuse to get Longhorn/Trusted Computing/NGSCB adoption mandated by regulation/legislation, all in the name of national security.

    30. Re:I'll be first to say it by JamesP · · Score: 1

      "Exploit found in Clippy anyone?"

      Try to picture something like this: MS Bulletin 12345-6

      "Clippy begins using innapropriate language"

      Description: Instead of helping the user in fulfilling his tasks, Clippy begins to swear and to misdirect the user. Mentions of another operational systems are frequent.

      --
      how long until /. fixes commenting on Chrome?
    31. Re:I'll be first to say it by Cyno01 · · Score: 1

      Thats actually possible with just a hex editor...

      --
      "Sic Semper Tyrannosaurus Rex."
    32. Re:I'll be first to say it by Anonymous Coward · · Score: 0

      I think companies are rushing out and buy Window XP - since exploits for NT and Window 2K are possible now. Microsoft might as well make NT and 2K a sunset product

    33. Re:I'll be first to say it by Pharmboy · · Score: 1

      Unless MS is trying to pull an SCO, I can't imagine a worst scenario.

      I posted something to this effect the other day. I am just wondering if MS is poisoning the waters for a potential post 2.6 lawsuit, claiming it used MS code just to slow adoption, while it releases its own BSD. They have talked about a console based server, they used to own a chunk of SCO stock, they did Xenix, have lots of BSD experience, and still use some BSD code. (ftp.exe for example). I also wonder if the money they recently paid SCO wasn't to help SCO as much as it was to get an unlimited Unix license, to prevent getting sued for any potential infringement. And they probably got it cheap, considering SCO needed the $$ badly. Having SCO then slow down Linux might have been just a bonus.

      If Apple can port NeXT (BSD) to Mac in a couple years, MS can certainly do the same in much less time, considering they are many times larger. Then they can look at GPL code for inspiration (read: not exact copy), but tweak it just enough to make it incompatible except to run some GPL stuff they don't want to have to support, like Mozilla. They have already said they will not be upgrading IE soon, just patches.

      --
      Tequila: It's not just for breakfast anymore!
    34. Re:I'll be first to say it by LousyPhreak · · Score: 1

      still better than if the office code had leaked:

      exploit found in clippy, you cannot disable it anymdamn get the hell away!
      no i don't want to type a letter!

      --
      -- Karma: beyond good and evil - mostly affected by posting political
    35. Re:I'll be first to say it by zero_offset · · Score: 1
      IF this is true, the release of the source is the nail in the coffin for Microsoft.

      Don't be stupid. Everyone knows that 90% or 98% or some-other-very-high-percentage of the world is using Windows. Only a tiny fraction will even hear about this and understand the potential -- and those people are most likely the same ones who are already inclined to distrust MS. (Or those who know what they're doing, and choose to trust MS anyway.)

      It's like the exploding Firestone tires on Ford Explorers. For the most part, it really didn't stop people from buying Explorers.

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  15. Smells by first.last · · Score: 0, Funny

    Smells like bullshit....like the jpeg virus hoax a few years back. IMAGE FILES CANNOT RUN COMMANDS!!!!

    --
    Wishing I was a millionaire since 1969.
    1. Re:Smells by Xeth · · Score: 5, Insightful

      They can if the tool you use to open them is ridiculously poorly designed and permits buffer overflow (i.e. IE).

      --
      If your theory is different from practice, then your theory is wrong.
    2. Re:Smells by Paladine97 · · Score: 5, Informative

      Well it's not really the image file running the commands. It's the browser that is loading the image. The browser reads bad image data and gets overwritten.

      It's no hoax.

    3. Re:Smells by Oscaro · · Score: 5, Informative

      Smells like you shoud read some documentation on buffer overflow techinques. Of course image files cannot run commands, but you can do some nice tricks if the program that is loading the file fails to check where the data is loaded. If the data is bigger than the allocated space, you can garble the stack in some funny way and actually craft a picture that gets to be executed (in some parts at least). Of course, doing something other that crashing the process is NOT easy, but...

    4. Re:Smells by Anonymous Coward · · Score: 0

      sorry, that smell is you.

      if the renderer is so poorly written that it can be attacked with an overflow bug then just guess how mocu other crap-quality code is in microsoft products...

    5. Re:Smells by Tasy · · Score: 0

      You are correct, data files can't run commands. That is not what the code does though. Read the article and you'll see:

      cbSkip = _bmfh.bfOffBits - cbRead;

      if (cbSkip > 1024)
      cbSkip = 1024;

      if (!Read(abDummy, cbSkip))
      goto Cleanup;

      The code parses the image data to a command that executes code. No hoax.

      --
      ------ ( Read More... | 666 of 682 comments )
    6. Re:Smells by sk8king · · Score: 2, Interesting

      The image file ISN'T running a command. I'm not claiming that I understand the code or what specifically triggers the problem [negative offsets or something], but there is something special about the bitmap image that causes the rendering program to break in such a way that data in the image can be copied into memory and then executed.

      Images are just data and everyone agrees with that, but you can display source code [C, perl whatever] as a bitmap file if you really want to, in numerous ways. Won't look like much, but you can't deny that the code is now a picture. Why can't a picture be formatted in such a way as to be interpreted as code.

      The problem here is the renderer [have I mentioned that already], not the picture.

    7. Re:Smells by Anonymous Coward · · Score: 0
      Good lord. You are a genius!

      *sighs condescendingly*

    8. Re:Smells by Doomstalk · · Score: 1

      So it's not the image file itself that executes the code. It tricks IE's image decoding algorithm into exceeding its memory bounds, writing whatever follows directly into RAM.

    9. Re:Smells by Anonymous Coward · · Score: 0


      Idiot.

      Save the snippet of code which has been posted here many times. Then, when you get to college in 8 years, you can ask your comp-sci teacher about it.

      Stupid fuck.

    10. Re:Smells by flossie · · Score: 1

      Image files cannot run commands!!!!

      Are you sure about that?

  16. Well I got IE6 by superpulpsicle · · Score: 5, Funny

    So I should be all set for the next 2 days until the next major security flaw is found.

  17. Anyone surprised? by LearnToSpell · · Score: 3, Funny

    Anyone? Come on, there's a million /. readers. Somebody must have thought this wasn't going to happen.

    Maybe the once-a-month patching schedule's going to have to be revised though.

    1. Re:Anyone surprised? by peragrin · · Score: 1
      Well my bet was placed for a week till the firest code exploit not 3 days.

      Wh wasn't this a slashdot poll, the day the source leaked, how long till a virus is written againist it????

      --
      i thought once I was found, but it was only a dream.
    2. Re:Anyone surprised? by cmburns69 · · Score: 1

      More often that once a month? Are you crazy? Most people can't even manage it twice a year!

      I know people say it's dangerous to run a computer without all the latest patches, but that doesn't really solve everything. Most virii are mostly based on social engineering (love bug, etc). The most recent large virus based only on a bug was Code Red, but it's patches had been available for months!

      As long as they include all that month's fixes, once a month is enough!

      --
      Online Starcraft RPG? At
      Dietary fiber is like asynchronous IO-- Non-blocking!
    3. Re:Anyone surprised? by SpaceLifeForm · · Score: 1
      It sure seems like the once-a-month patching schedule has already been obsoleted by MS before this source code release. Of course I don't really keep track since it's just too much work. I do point them out occasionally to some friends that are still addicted to MS. The subject line in my e-mail to them is YAME - Yet Another Microsoft Exploit.

      They're starting to 'get it'.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
  18. But the question is... by Xeth · · Score: 4, Insightful

    ...if the code was open from the start, how long would this flaw have lasted?

    --
    If your theory is different from practice, then your theory is wrong.
    1. Re:But the question is... by lintux · · Score: 5, Insightful

      Yeah, but I don't expect the Microsoft PR-team to talk about that in their anti-OSS campaigns...

    2. Re:But the question is... by Apiakun · · Score: 3, Funny

      And the other question: How long would Microsoft have lasted?

    3. Re:But the question is... by Xeth · · Score: 3, Interesting

      As long as RedHat and SuSe? Sure, they might not have a stranglehold on the market like they do now, but they'd likely turn a profit.

      --
      If your theory is different from practice, then your theory is wrong.
    4. Re:But the question is... by Nothinman · · Score: 3, Insightful

      The real question is what SP level was this fixed at? IE6 isn't vulnerable and I believe the leaked Win2K code was only SP1, so that means there's 3 SPs and all of them include IE so there's no telling when, if at all, the bug was fixed.

    5. Re:But the question is... by sql*kitten · · Score: 2, Informative

      if the code was open from the start, how long would this flaw have lasted?

      Umm, probably about as long as the flaws in sendmail and bind?

      Open source is not a panacea, those two packages alone have accounted for more Internet carnage than any bug in an MS product. And they were open source, full of bugs, and no-one fixed them.

      See, this "many eyes" argument only works if many eyes are looking at the code, whereas in practice everyone assumes that everyone else is, so they don't need to worry about it.

      It is also worth noting that the source of the leak was traced to a Linux box at a company called MainSoft, who licensed the code to write their cross-platform toolkit MainWin.

  19. Boogle... by mark_space2001 · · Score: 2, Funny
    I guess I should have expected that someone would start posting bug fixes to Windows when I heard that the code was got released, but I'm still surprised that they are finding actual exploits in the code.

    I guess all those advertising^W software engineering dollars that MS spent on their security inititive were not^W well spent.

    1. Re:Boogle... by kyndig · · Score: 1

      What's even more concerning is that the exploit affects such an older version of Internet Explorer. This would indicate that the developers have their eyes focused forwards, and do not take into account backwards compatibility or security concerns. MS incorporates their "stuff" too much into their OS to not take into account how it would affect older systems. While you can't even find downloads for Windows 95 or 3.1 these days, I don't doubt that there's an old Win95 box browsing the internet somewhere right now with its 28 baud modem., and most certainly running an IE 5 version.

      --
      My Thoughts, Kyndig
  20. And awaaayyy we go! by dogas · · Score: 2

    And so it starts. How many of these exploits will be found based upon the source? Tons?

    Just how bad is the source that a whole lot of exploits like these can be written? I wonder what this means for MSFT.

    Can the same thing happen to linux? Or do exploit authors prefer windows?

    --
    'When the going gets weird, the weird turn pro.' -HST
    1. Re:And awaaayyy we go! by Anonymous Coward · · Score: 0

      Well, in the case of popular open source software most stupid bugs like this have probably been found already. If Linux had been developed behind closed doors to its current size and complexity, and then suddenly released like this, you can bet there would have been a lot of problems found and probably exploited.

    2. Re:And awaaayyy we go! by 1000101 · · Score: 2, Interesting
      "Can the same thing happen to linux? Or do exploit authors prefer windows?"


      IMHO exploit authors prefer windows simply because they want to maximize their impact. Why spend all those hours writing a virus when it will only cause problems for a few percent of the computers out there. I would think they get much more satisfaction when they see "500 million" machines infected on CNN.

    3. Re:And awaaayyy we go! by Dalcius · · Score: 2, Interesting

      I think you'll find that the more 'serious' crackers who aren't interested in harvesting boxes for DDoS purposes will be going after servers. And looking at how many servers run *NIX, Linux is going to be a very popular target, especially since many services are shared.

      With high quality crackers going after Linux boxes, I think either A) somehow nobody outside of the cracker community hears about exploits and companies are keeping quiet when they get hit, or B) OSS really does have an edge.

      I'm more inclined to believe the latter.

      Cheers

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    4. Re:And awaaayyy we go! by bshroyer · · Score: 2, Funny

      Can the same thing happen to linux?

      Yeah, let's hope that the source code for Konqueror or Mozilla never gets leaked... No telling what kinds of exploits might pop up then.

      --
      The cure for cancer is coming: Reovirus
    5. Re:And awaaayyy we go! by seanvaandering · · Score: 1

      Can the same thing happen to linux? Or do exploit authors prefer windows?

      Yes, of course it can happen in Linux, but heres the clincher - as soon as its found in linux, its patched instead of someone coding an exploit - spreading it around until some sysadmin gets pissed off and codes a patch for it. Which is probably why viruses in OSS are rare, because why try? It's going to get patched before any widespread infection can occur, and most users on the Linux platform are smart enough to stay up to date anyways.

      Windows OTOH is a 6 month turnaround or more and your controlled by an entity whos decisions are based around profitability. If its more profitable to keep an exploit open on a O/S and get some nice contracts with some Anti-Virus companies for another couple months, then thats cool - unfortunately for the luser - this is a no win situation, and they have absolutely NO control over their computer.

      To say this exploit isn't going to affect anyone is ignorant - There are still quite a few people using IE 5, granted about 20% of the entire IE surfing public, according to some of my weblogs.

    6. Re:And awaaayyy we go! by Anonymous Coward · · Score: 0

      Riiiight. Like all of the UNIX and Linux Apache servers out there wouldn't be a PRIME target for DDOS and other exploits, considering that the majority of them have their own private high-speed LAN through several gigabit ethernet pipelines.

      Some of you guys really need to think about this. The same thing WON'T happen to Linux because the degree of bugs in key components are not nearly at the same degree of those in Windows code.

    7. Re:And awaaayyy we go! by mdfst13 · · Score: 2, Insightful

      Then how do you explain Nimda and SQL Slammer? Both of those affect Microsoft products (and their vulnerabilities) that are in the *minority* of those available. Apache trounces IIS in usage numbers (both because more web sites using it and because higher traffic web sites use it), and any of MySQL, Oracle, or IBM (I forget the actual name) outnumbers Microsoft SQL Server.

      IMnsHO, exploit authors prefer Microsoft Windows products because they are buggy (note that the posted exploit actually affects a discontinued product, it lasted that long), because they are based on a buggy security model (oh, you are code? I'll run you automatically and save asking the user if he/she wants to run something from "MLM will make you millions!"), and because they are commonly used by people who don't know what they are doing. Any twit can install IIS--it's just a matter of following prompts. With Apache, you need a certain level of knowledge; particularly if you are not happy with the default settings and want to change them (especially the compiled in settings, which can obviously only be changed by recompiling the software; Microsoft writes that stuff out and makes it configurable, since they don't allow you to compile things).

    8. Re:And awaaayyy we go! by otis+wildflower · · Score: 2, Informative

      Windows OTOH is a 6 month turnaround or more and your controlled by an entity whos decisions are based around profitability. If its more profitable to keep an exploit open on a O/S and get some nice contracts with some Anti-Virus companies for another couple months, then thats cool - unfortunately for the luser - this is a no win situation, and they have absolutely NO control over their computer.

      Not to mention the risk admins take when applying patches, which can disable apps or change bug behaviors that critical apps wrongfully rely on. Not to mention either that historically service packs have not been 100% reliable to boot.

      The sad thing is, you can be a perfectly good, clued person stuck with admining critical functions on M$ boxes (that you inherited based on decisions you had no influence over), and let patches sit for weeks or months waiting for others to try them out. Security patches included, since M$ is so spaghetti that one security fix can break or alter behavior in other areas nearly nondeterministically. Luckily, I've never had to worry personally about a windows box for my job security: in the cases I may have had to do so I've been able to build lower-cost and higher-function/reliability OSS solutions and sleep soundly at night.

      There's a reason why they're called 'Suicide Packs' by those poor souls whose jobs rely on M$ stability and security...

    9. Re:And awaaayyy we go! by ddear · · Score: 1

      MySQL? Are you kidding? Nothing against the product, but there is not a chance in hell its market share is higher than SQL Server.

      First of all, SQL Server has 20% market share across Windows and UNIX, and is the leader (with over 40% I believe) on Windows.

      That is for purchased licenses. Also, everybody seems to somehow get MSDE (the free front-end-less version of SQL Server) installed. MSDE is as easy to install as IIS. Take that into account and I'll bet that the actually number of installed instances probably vies for first with either Oracle or DB2.

      I'm not saying this is a good thing. The fact that so many desktops get a web server and network-aware RDMS service running on them is just frightening. But I do think that the sheer number of machines out there has an affect on what systems people try to attack. Couple that with the fact that MS is the company that people love to hate, and I'm sure you have a lot more effort going into writing exploits for Windows/IIS/SQL/etc than for MySQL.

    10. Re:And awaaayyy we go! by bonch · · Score: 1

      I guess you missed the article Slashdot posted a while back that actually showed that because Linux was the most-used OS on the net, it was also the most-breached.

      I also think the fact that GNU got hacked twice, Debian, Gentoo, and GNOME were also compromised, all in the span of six months in 2003, one should take pause and note that things are only as secure as their admins.

  21. Microsoft wants us to upgrade to XP by Anonymous Coward · · Score: 3, Insightful

    Microsoft code must be so ridden with bugs to create a exploit in just a week.
    Or maybe it is a ploy by microsoft to force users to upgrade to XP

  22. Bugs by Agent_Number_4 · · Score: 5, Insightful
    This is just the tip of the ice-berg, just imagine what could be done if the whole code was released, and included source for XP.

    I for one am truly alarmed and cannot wait for Microsoft to start the repairs; but then again this is good news for MS programmers looking for OT.

    1. Re:Bugs by Anonymous Coward · · Score: 0

      "I for one am truly alarmed and cannot wait for Microsoft to start the repairs"

      RTFA; it is already fixed

    2. Re:Bugs by mhayenga · · Score: 1

      Yep... Nothing makes filling up the OT time card like hours upon hours of writting buggy, exploitable code :)

      I can see their eyelids sagging now :)

      ----
      Man, hope I get that MS interview next week :)

  23. GTA by W32.Klez.A · · Score: 0, Redundant

    From the article:

    Date: Sat, 14 Feb 2004 22:08:59 -0800
    From:
    Subject: [Full-Disclosure] GAYER THAN AIDS ADVISORY #01: IE 5 remote code execution


    Someone should remark to Security Tracker to maybe have some discretion when posting their information.

    1. Re:GTA by Anonymous Coward · · Score: 0

      Thank you, Hitler...

    2. Re:GTA by Anonymous Coward · · Score: 0

      Gays suck, so what your problem? Are you gay or something?

    3. Re:GTA by Maserati · · Score: 1

      A new word has been coined, "ghey" that they might have used instead. It's a little less of a 5th-grade insult anyway.

      That said, call it what you will - but being able to execute arbitrary code by massing a malformed .bmp is pretty bad.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  24. Let the Hacking Begin! by stibles · · Score: 1

    I wonder how many flaws will be exposed in the next week? over the next month? Kinda like a Pandora's Box. "You can't take it back because it's already out there." - Harry, When Harry Met Sally The real question is who is the bigger loser, Microsoft or Diebold? "Who's the big winner here at the casino tonight? Mikey, that's who!" - Trent, Swingers Or the public at large...

  25. Leak a good thing for MS by kyndig · · Score: 5, Insightful

    It was only 15% of the source code which leaked out, yet it will show MS in the weeks to come just how the Open Source community operates. I forsee them working over time to provide updates to the numerious vulnerabilities which will arise due to the leaked code. This here is just one example. There were some what, 3 million lines of code in the leaked source. It is just a matter of time. Hopefully folks will report the vulnerabilities which they find, opposed to exploiting them.

    --
    My Thoughts, Kyndig
    1. Re:Leak a good thing for MS by Savant · · Score: 5, Insightful

      And yet those who contact Microsoft with patches for the leaked code are marking themselves as individuals who've read that code. As such, they are now fair game for Microsoft should they ever work on a piece of open source or commercial software that duplicates in some way functionality present in Windows.

      I'm staying away from the code, and if I were ever tempted to look at it and did discover a vulnerability, I certainly wouldn't release a patch with my name attached.

    2. Re:Leak a good thing for MS by orthogonal · · Score: 2, Insightful

      It was only 15% of the source code which leaked out, yet it will show MS in the weeks to come just how the Open Source community operates. I forsee [sic] them [open source coders] working over time to provide updates to the numerious [sic] vulnerabilities which will arise due to the leaked code.

      (I'm pretty sure the OP means "open source coders" by "them" not "Microsoft's coders". So...)

      Fu^H^HScratch that dude.

      I code for pay, or I code because I get to use the code as I wish. I'm not coding anything for free for Microsoft to keep as proprietary.

      Even worse, anyone who does look at the stolen Microsoft source can't work on any code to which they attach their own copyright -- whether GPL'd or their own propriety license -- that has similar functionality to Microsoft's stolen source, for fear of tainting their project and opening it to claims it uses stolen Microsoft "Intellectual Property".

      Open source doesn't operate on stolen code, and open source isn't some great big altruistic charity project designed to rescue any arbitrary buggy proprietary code.

      Open source is about working on our own code, and owning our own code. That we license it so that you can use it too doesn't -- Darl McBride's "unconstitutional" claims to the contrary -- make it any less our property; it just means that we have different goals (like attracting talent to work with us, and getting bragging rights, and perhaps tentative tries at ushering in a world much less controlled by scarcity), and are leveraging our ownership to reach those goals.

      Microsoft can fix their own code, and godspeed to them.

    3. Re:Leak a good thing for MS by stratjakt · · Score: 1

      Yeah, just how it operates:

      "MS IS GAYER THEN AIDS!!!11!!!1! OMFG LOLOR U R TEH SUCK!!1!!'

      Dedicated professionals my ass.

      --
      I don't need no instructions to know how to rock!!!!
    4. Re:Leak a good thing for MS by inode_buddha · · Score: 2, Interesting

      It's got to be interesting to run over the whole thing with something like valgrind. Not that I'm going to try, nor do I want a copy of their code anywhere near me.

      --
      C|N>K
    5. Re:Leak a good thing for MS by Anonymous Coward · · Score: 0
      "MS IS GAYER THEN AIDS!!!11!!!1! OMFG LOLOR U R TEH SUCK!!1!!' Dedicated professionals my ass.
      in this context you really don't want to be talking about your ass.
    6. Re:Leak a good thing for MS by SirSlud · · Score: 2, Insightful

      > Even worse, anyone who does look at the stolen Microsoft source can't work on any code to which they attach their own copyright -- whether GPL'd or their own propriety license -- that has similar functionality to Microsoft's stolen source, for fear of tainting their project and opening it to claims it uses stolen Microsoft "Intellectual Property".

      You could have just said: out judicial system is broken. This is akin to musicians not looking at each others sheet music because we're afraid BMG would sic their lawyers on us for using that F# in our original song. So much for the innovation, competition, and peer review that has led to North America being one of the more technologically advanced societies. It's like we're throwing the baby out with the bathwater, nevermind that the baby got us here in the first place.

      --
      "Old man yells at systemd"
    7. Re:Leak a good thing for MS by verbatim_verbose · · Score: 1

      The Open Source community? This is a pretty confused comment you make... the source here wasn't and still isn't open. Most people in the open source community will want nothing to do with it, as the legal ramifications of even downloading it are quite questionable. Also, what's the motivation to put effort into fixing something like this?

      The only thing being demonstrated is that those who consider themselves part of the open source community are using this opportunity to go try to one-up Microsoft.

    8. Re:Leak a good thing for MS by Anonymous Coward · · Score: 0

      I just posted a chunk of it on theyre blogs.msdn.com

      SO fuck, every cat and theyre dog has it.

  26. let the games begin by joeldg · · Score: 0, Redundant

    all I can say is let the games begin..
    who cares how/why it got it out..

    it is out..

    and every guy out there looking for the latest 'sploit' will be oggling the code to find just what happens in 'that one key segment' that has been slowing them down..

    Soooo glad I am all linux..

  27. Dear Mr. Gayer Than Aids by Anonymous Coward · · Score: 0

    How can a virus be gay? Just shows it doesn't take a genius to find an integer overflow in source.

    1. Re:Dear Mr. Gayer Than Aids by Satan+Dumpling · · Score: 0, Offtopic

      How bout if the virus changes your homepage to hotgaymen.com? Then it's probably gay. :)

  28. Text of advisory by Anonymous Coward · · Score: 4, Informative
    I downloaded the Microsoft source code. Easy enough. It's a lot
    bigger than Linux, but there were a lot of people mirroring it and so
    it didn't take long.

    Anyway, I took a look, and decided that Microsoft is GAYER THAN AIDS .
    For example, in win2k/private/inet/mshtml/src/site/download/imgbmp .cxx:
    // Before we read the bits, seek to the correct location in the file
    while (_bmfh.bfOffBits > (unsigned)cbRead)
    {
    BYTE abDummy[1024];
    int cbSkip;

    cbSkip = _bmfh.bfOffBits - cbRead;

    if (cbSkip > 1024)
    cbSkip = 1024;

    if (!Read(abDummy, cbSkip))
    goto Cleanup;

    cbRead += cbSkip;
    }
    .. Rrrrriiiiggghhhttt. Way to go, using a signed integer for an
    offset. Now all we have to do is create a BMP with bfOffBits > 2^31,

    and we're in. cbSkip goes negative and the Read call clobbers the
    stack with our data.

    See attached for proof of concept. index.html has [img src=1.bmp]
    where 1.bmp contains bfOffBits=0xEEEEEEEE plus 4k of 0x44332211.
    Bring it up in IE5 (tested successfully on Win98) and get
    EIP=0x44332211.

    IE6 is not vulnerable, so I guess I'll get back to work. My Warhol
    worm will have to wait a bit... .gta
    PROPS TO the Fort and HAVE IT BE YOU.

    1. Re:Text of advisory by Bigbowser · · Score: 4, Interesting

      dumbasses..... but doesn't posting that source code there makeslashdot liable to microsoft's evil wrath?

      --

      Bigbowser.
    2. Re:Text of advisory by Anonymous Coward · · Score: 0

      yeah, really. Code that bad could prove to be a big embarassment to Microsoft.

    3. Re:Text of advisory by myowntrueself · · Score: 1, Funny

      So now the /. servers are going to be raided by DMCA police? Time to move offshore, guys! ;)

      --
      In the free world the media isn't government run; the government is media run.
    4. Re:Text of advisory by adrianbaugh · · Score: 1

      Since it's less than 10% of the total, and slashdot never signed an NDA, doesn't it count as fair use? Or is there some kind of weird exception for code?

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    5. Re:Text of advisory by AstroDrabb · · Score: 5, Interesting

      You are allowed to use copyrighted information to some extent for certain purposes such as educationl, parady, etc. You can use a small clip from a song, you can display a paragrahp from a book, etc. I doubt anyone would consider showing 10 lines or so of source code out of millions a copyright violation. The grandparent post is obviously for education purposes only : )

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    6. Re:Text of advisory by grub · · Score: 5, Funny


      I doubt anyone would consider showing 10 lines or so of source code out of millions a copyright violation

      SCO does. :)

      --
      Trolling is a art,
    7. Re:Text of advisory by syzme · · Score: 1

      I was reading the newsclips from the FBI on the matter, and they would definately disagree. The code is a trade secret, and it is therefore illegal to just posses it. Slashdot could very easily be screwed now if M$ is pissed.

    8. Re:Text of advisory by SmackCrackandPot · · Score: 2, Interesting

      How many people haven't tried writing their own image file read/writers, got a few conditionals wrong up and written out a dodgy image file that crashes their own applications, the PC let alone the desktop.

      Given Windows XP ability to display thumbnail views of JPG's, TIF's and MPG's (even though it can display the first frame of MPG-2, but not actually play the movie), there could be some serious fun to be had there...

    9. Re:Text of advisory by Anonymous Coward · · Score: 1

      Could someone explain exactly what happens in this code that causes the overrun ?

    10. Re:Text of advisory by TedCheshireAcad · · Score: 1

      You are allowed to use copyrighted information to some extent for certain purposes such as educationl, parady, etc.

      ....this snippet is a parody of itself.

    11. Re:Text of advisory by surfcow · · Score: 0, Offtopic
      Anyway, I took a look, and decided that Microsoft is GAYER THAN AIDS .

      Brother, I understand your point, but I really don't like the way you express it. At all.

      I would really like to keep this kind of crap off slashdot. The rest of the internet is a toilet. Save it for there. Thanks.

    12. Re:Text of advisory by adrianbaugh · · Score: 4, Interesting

      Ah, OK. Is there any well-defined point at which it ceases to be a trade secret (on account of everyone and his dog having a copy[0])?
      Also, is it slashdot, the comment poster, or both, who is screwed?

      [0] Note: I don't have a copy.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    13. Re:Text of advisory by Anonymous Coward · · Score: 0

      You obviously don't read slashdot at -1 very often. Assmaster.

    14. Re:Text of advisory by prockcore · · Score: 3, Funny

      Oh my god! I read the source! Now I'm tainted! All future code written by me will inadvertantly contain MS's copyrighted and patented signed int overflow techniques!

    15. Re:Text of advisory by Anonymous Coward · · Score: 0

      thanks to you i can't work on wine anymore. thanks dildo.

    16. Re:Text of advisory by Bigbowser · · Score: 1

      This is microsoft remember, they'd sue you if you made a parody of them, for microsoft 10 lines is enough to hang you for.

      --

      Bigbowser.
    17. Re:Text of advisory by Anonymous Coward · · Score: 1, Funny

      Thanks to Microsoft AutoParody Wizard!

    18. Re:Text of advisory by Anonymous Coward · · Score: 0

      Hey surfcow, you forgot the link to your organization...

      http://www.nrb.org/

      Let's shut them all down my Droogy! Death to the ones who don't think like us!

    19. Re:Text of advisory by black+mariah · · Score: 1

      As if they didn't already have enough fuel from the "Microsoft abuses human rights in China" headline a few days back. But they don't give a shit.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    20. Re:Text of advisory by Anonymous Coward · · Score: 5, Informative

      Could someone explain exactly what happens in this code that causes the overrun?

      Yes. I'll assume you're familiar with the basic ideas of programming, but are unfamiliar with C, especially on x86. I'll also assume you're familiar with hexadecimal/binary notation, as I'll be using it.

      on x86, a negative integer is represented somewhat oddly. In C, the 'int' datatype is signed, meaning it can represent 'negative' integers. Specifically, the way a 16 bit signed integer is represented on x86 (and hence, how C compilers for x86 are going to handle them) is this:

      Convert -3 to positive, so we have 3.
      3 is represented as this (16 bit signed integer) :
      0x0003
      or in binary - 0000 0000 0000 0011

      to get the negative representation, we flip every bit and add 1. so, the representation of -3 in a 16 bit signed integer on x86 is:
      1111 1111 1111 1100 + 1 = 1111 1111 1111 1101
      which in hexadecimal is 0xFFFD. note that, 0xFFFD is large (relative to the max value 16 bits can hold). if treated as unsigned, specifically represents the number in base 10 as 65533.

      now with that aside, we can easily spot the problem.

      /* cbSkip represents a signed integer */
      int cbSkip;

      /* bfOffBits is supposed to be unsigned. */
      cbSkip = _bmfh.bfOffBits - cbRead;

      /* if bfOffBits say, contains 0xFFFF (-1)
      than cbSkip _wont_ be greater than 1024,
      note that this is supposed to prevent
      too many bytes to be read! */
      if (cbSkip > 1024)
      cbSkip = 1024;

      /* Since cbSkip contains 0xFFFF, which is '-1',
      Read will attempt to read 0xFFFF bytes into
      the buffer, which can only store 0x400 bytes.
      Oops. */
      if (!Read(abDummy, cbSkip))
      goto Cleanup;

      The technical reasons of why overwriting a buffer is bad, are beyond the scope of this post. Just know that it is one of the worst things that can happen ;)

    21. Re:Text of advisory by Anonymous Coward · · Score: 0

      "You are allowed to use copyrighted information to some extent for certain purposes such as educationl, parady, etc."

      Not if you illegally acquired it.

    22. Re:Text of advisory by Anonymous Coward · · Score: 2, Funny

      worse than that, it contains a "goto" statement... *shudder*

    23. Re:Text of advisory by Anonymous Coward · · Score: 0

      The code was a trade secret. Trade secret law is very clear that once something isn't a secret it can't be a trade secret.

    24. Re:Text of advisory by utlemming · · Score: 1

      Well, even Microsoft goes after people for parody -- remember www.mikerowesoft.com? Yeah, that would be a clear case of parady, but M$ called it copyright infringement.

      --
      The views expressed are mine own and do not express the views of my employer.
    25. Re:Text of advisory by dylan_- · · Score: 4, Informative
      The technical reasons of why overwriting a buffer is bad, are beyond the scope of this post. Just know that it is one of the worst things that can happen ;)
      I'll have a go at a simple explanation....

      The data fills up all the room that was allocated for it and then carries on. You make sure there's enough that it overwrites a special bit of memory called the EIP which tells the computer where the next intruction in memory is. So you make sure the data that lands in the EIP points to the data (actually instructions) you've kindly provided! Whatever process you've overrun has now been hijacked and your code is running. Make sense?
      --
      Igor Presnyakov stole my hat
    26. Re:Text of advisory by ktulu1115 · · Score: 1
      Also, is it slashdot, the comment poster, or both, who is screwed?
      Actually, it'd be all of us since it's now stored in our browser's cache.
      --
      # fuser -v /dev/attention | grep work
      #
    27. Re:Text of advisory by PhilHibbs · · Score: 4, Informative
      that it overwrites a special bit of memory called the EIP
      No, it doesn't overwrite the EIP, that's a register in the CPU. What it does overwrite is the return address that was pushed onto the stack when the function was called, so instead of returning to the calling code, it returns to the exploit code.
    28. Re:Text of advisory by Rip!ey · · Score: 1

      The code is a trade secret ...

      Not any more.

    29. Re:Text of advisory by Exitthree · · Score: 1

      The usual disclaimer is that I am not a lawyer. However, I have some familiarity with the law.

      The uses of copyrighted material you mention are defensible under fair use and de minimus arguments, however, this is not a copyright argument. The source code is protected as trade secret, which means that it is illegal to display it as long as the owner of the trade secret (Microsoft) has gone to reasonable efforts to keep the code secret. Reproduction or display of any part of the code is a violation of Microsoft's trade secrets.

    30. Re:Text of advisory by Anonymous Coward · · Score: 0

      did you geniuses ever stop to consider maybe they do a sanity check against bfOffBits > 2^31 when the bitmap header is first read in? it's rather absurd to post a while loop completely out of context in an attempt to prove your point.

    31. Re:Text of advisory by Reemi · · Score: 1

      if (!Read(abDummy, cbSkip))
      goto Cleanup;


      GOTO considered harmful.

    32. Re:Text of advisory by flossie · · Score: 1
      The technical reasons of why overwriting a buffer is bad, are beyond the scope of this post. Just know that it is one of the worst things that can happen ;)

      The technical reasons of why overwriting a buffer is bad are described here

    33. Re:Text of advisory by Bamafan77 · · Score: 1

      now with that aside, we can easily spot the problem.

      To me the key is to know that the call to Read treats the second parameter as an unsigned hexadecimal number rather than a signed hex. I had trouble understanding your explanation until I realized you had to have made this assumption. The rest was terrific though. Interesting stuff.

      It's not obvious if you don't have this kind of training that warns about this specific exploit, specifically with x86 systems. To spot it on your own would require several levels of thinking that nobody (talking untrained here) would do on their own in a complex system. So, this is something you'd have to deliberately be looking out for. To call someone making this mistake stupid seems silly (not talking to parent here, but to some other replies).

    34. Re:Text of advisory by dasmegabyte · · Score: 1

      Note: I don't have a copy.

      Does your dog?

      --
      Hey freaks: now you're ju
    35. Re:Text of advisory by mindriot · · Score: 1

      I think they just missed Microsoft's most important code line in ms.h:

      #define int unsigned int

      Lame joke, I know :)

    36. Re:Text of advisory by Anonymous Coward · · Score: 0

      What's interesting is that the programmer foresaw a potential for the offset to reach past the temp buffer, but did not consider a negative offset. Oops.

    37. Re:Text of advisory by syzme · · Score: 1

      I'm not a legal expert, but I would assume that there is a pretty clear line that was crossed between when only MS employees could view the code, and when the code was realeased for anyone on the Internet to view.

      The second point you bring up is more interesting. who exactly is going to be recieving the screwing from MS? I'm not sure, but you might be able to extend the precedent which is going to be set down in that file sharing case which is comming up about whether the owner of an Internet "commons" can be held responsible for the actions of its users.

    38. Re:Text of advisory by bonch · · Score: 1

      "Gayer than AIDS?"

      Not only is it extremely juvenile to label things "gay," but lots of people who have AIDS aren't homosexuals.

      I would have figured Slashdot would be posting things at least a little more mature than a SomethingAwful post.

    39. Re:Text of advisory by nash · · Score: 1

      I'm curious how "2's Compliment" representation can be considered "Somewhat Oddly".

      It is _the_ monst common method of representing negative numbers on fixed point (ie integers) on the planet.

      The reason is quite simple: You can perform arithmetic without having to adjust for signs or check for them. The only thing you need to do is check for overflow, which can be done automatically.

      This results in tremendous speed advantages over systems such as signed magnitude.

    40. Re:Text of advisory by AstroDrabb · · Score: 3, Informative

      I actaully read that in the EULA for MS Front Page you are not allowed to use Front Page to make any site that is demeaning to microsoft, and by using MS Front Page, you agree to not make any negative sites about MS.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
    41. Re:Text of advisory by fermion · · Score: 1
      IANAL, but fair use appears to be a fluid issue. Some comics license the material they parody. Sometimes it is ok to copy an article, sometimes not. It is ok to show a movie related to the subject in a formal classroom setting, but show Finding Nemo without a license and trouble may ensue.

      MS could and would certainly sue on a number of fronts for the publication of the code. The 10 line defense would probably not fly in court.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    42. Re:Text of advisory by Anonymous Coward · · Score: 0

      That is freedom!. The Bigest pocket freedom will prevail over the others freedom.

    43. Re:Text of advisory by Blackhalo · · Score: 1

      Ah, but is it even copyrighted? I thought propriatary source was more of a trade secret? Was the source officially published? I think that is what you do to get the defacto copyright. Is not that the tradeoff? Publish publicly the IP and you get copyright protection? Is this not more like CSS which is not more or less public domain now?

      --
      "There is nothing to do it. But to do it." -Floyd Pepper
  29. Outbreak and email renderer by secondsun · · Score: 4, Insightful

    If you were to embed myDoom after the overflow area in the bitmap then when outlook opened the file using ie's render could one have my doom that didn't even need to have the end user open the file? It would just execute replicate, then piss people all to hell? For that matter could I include the windows equivalent of rm -rf / ?

    --
    There is nothing wrong with being gay. It's getting caught where the trouble lies.
    1. Re:Outbreak and email renderer by Phillup · · Score: 5, Insightful

      Congrats... you are the first post I've seen that gets one of the very important points.

      I've seen everyone say that IE 6 isn't vulnerable... and all I keep thinking is: Not to this particular instance of the exploit. That doesn't mean it is free of problems from this class of exploits.

      But, you can bet that the person that wrote this one little bit of code wrote a lot of other code. So, what you have in front of you is a class of problem that can be tried over the entire binary code base. You now know that one image handling routine is succeptible to this flaw... and now you can start targeting them all. Without needing access to the source code for that part of the software.

      Know how many times Windows (a graphical user interface) handles bitmapped files? Every one of those is a possible point of failure that you don't need the source code to find... simply start feeding something like this bmp to each of them.

      Automated testing at it's finest.

      --

      --Phillip

      Can you say BIRTH TAX
    2. Re:Outbreak and email renderer by mrseigen · · Score: 1

      Bingo. You got it; chances are this kind of thing is still present in a lot of newer software (especially now that damn near everything in userland is based on the same HTML/Explorer modules).

    3. Re:Outbreak and email renderer by Reziac · · Score: 1

      Well, you're right good for a sinking feeling :(

      Applications generally use the Windows internal bitmap renderer, right? so this could potentially be triggered from anywhere, not just from IE itself?

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  30. A quick look at the source code by Jacco+de+Leeuw · · Score: 5, Interesting
    Kuroshin has an article about the source code:

    "In short, there is nothing really surprising in this leak. Microsoft does not steal open-source code. Their older code is flaky, their modern code excellent. Their programmers are skilled and enthusiastic. Problems are generally due to a trade-off of current quality against vast hardware, software and backward compatibility."

    But this IE exploit shows that the author was wrong on at least one account:

    "The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places. The amount of networking code here is small enough for Microsoft to easily check for any vulnerabilities that might be revealed: it's the big applications that pose more of a risk. This code is also nearly four years old: any obvious problems should be patched by now".

    --
    -------
    Warning: Slashdot may contain traces of nuts.
    1. Re:A quick look at the source code by ymgve · · Score: 2, Insightful

      He was right. Reading a bitmap has NOTHING to do with networking code.

    2. Re:A quick look at the source code by W2k · · Score: 5, Insightful

      But this IE exploit shows that the author was wrong on at least one account.

      Wrong. He was right. This particular IE exploit has been fixed; it only affects an old version of IE. And IE is free, so there's no real excuse for not upgrading it. If I found a bug in an older version of an open-source app, and filed a bug report on it despite the fact that it had been fixed AGES ago in a newer version, I think I would be told to shut the fuck up and upgrade with little or no delay.

      --
      Quality, performance, value; you get only two, and you don't always get to pick.
    3. Re:A quick look at the source code by MrScience · · Score: 1

      Wait, I don't get it. How was he wrong? The overflow doesn't happen in newer versions of IE, and it could also be argued that IE is one of the "bigger" programs at a higher risk, as it is not "simpler network code".

      --

      You quitting proves that the karma kap worked. The most annoying of the whores shut up. --CmdrTaco

    4. Re:A quick look at the source code by Karth · · Score: 2, Interesting

      Well, the question here is not whether it's been fixed in IE 6, it's whether it's been fixed in IE 5.5. Anyone with Windows 98SE down cannot upgrade to IE6. It won't run on 98SE or below, where IE 5.5 can.

    5. Re:A quick look at the source code by Anonymous Coward · · Score: 0

      I Agree With This Post.

      While it's technically true that IE 5.01 is still supported (on base W2K configs only), realistically they aren't patching it very frequently. (It only seems to get backported security patches with service packs.)

      If you care about security, you aren't running IE5.

      (A good analogy is finding a bug in Mozilla 1.0x -- Mozilla.org will get around to patching it, but realistically everyone has moved on by now.)

    6. Re:A quick look at the source code by Jacco+de+Leeuw · · Score: 2, Interesting

      Well, the author wrote: "The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places". I found that a bit ironic because the next day an exploit was found.

      Although an exploit was found, the security risk is low. That's probably true, because most people have upgraded from IE 5.x to 6.x or some other browser.

      Still, I just checked the stats on a webpage about a moderately advanced security topic that I recently made. It turns out that almost 5% of the visitors use IE 5.x. Yikes...

      --
      -------
      Warning: Slashdot may contain traces of nuts.
    7. Re:A quick look at the source code by JustKidding · · Score: 3, Insightful
      Well, yes, ofcourse you could say that the fix is upgrading to IE 6.0. Too bad you can't install IE 6.0 on NT 4.0, no matter what service pack you have.

      So you say the fix would be to upgrade to XP? That's far from free, and most machines running NT 4.0 now are to old to run XP. Besides, why upgrade when the OS you have does everything you need it to do?

      Your analogy with open-source apps isn't right either. The 2.0 linux kernel, for example, is many years old now, but it's still being maintained and patched when needed.

      How on earth could this little gem make it past QA? You'll have to admit it's pretty easy to spot when you're looking for vulnerabilities.

    8. Re:A quick look at the source code by SoTuA · · Score: 2, Interesting

      Upgrading isn't always an option. For example, at work we have a system that relies heavily on specific versions of Apache and Perl. But, the Apache and Perl teams still patch bugs in my "old" versions of the software.

      I don't have this option with MS.

    9. Re:A quick look at the source code by W2k · · Score: 1

      The "fix" could just as well be switching browsers to Mozilla. Note that Microsoft does _not_ force you to use IE, it just ships Windows with IE as the default. So what if you can't upgrade IE, replace it instead. Yes, IE will still be there, but for websurfing (which is where you would most likely encounter this particular exploit) it wouldn't be used, and thus it would be harmless.

      There's also a world of difference between a web browser and a kernel. The 2.0 kernel is still updated yes, but can the same be said for every major open source application, regarding the version which was current in the year 2000? I doubt it.

      --
      Quality, performance, value; you get only two, and you don't always get to pick.
    10. Re:A quick look at the source code by Dahan · · Score: 1
      Too bad you can't install IE 6.0 on NT 4.0, no matter what service pack you have.

      Why can't I? I've done it before... is MS going to DMCA me now or something? No, their system requirements page even says it's supported on NT 4.0 SP6a.

    11. Re:A quick look at the source code by CmdrDude · · Score: 1

      That's funny... If that was true then how come I'm able to run IE6 on Win98SE? I think you mean IE6 won't run on anything less than win98.

    12. Re:A quick look at the source code by ksemlerK · · Score: 1

      Yes, you can install IE6 on Windows NT 4.0. Although to do so, you must have SP 6a installed. If you were reffering to Windows 95, you would be correct. Windows 95 only allows the installation of IE 5.5 SP2 or lower.

    13. Re:A quick look at the source code by Karth · · Score: 1

      agh. You're right. It's been a year since I took a technical support call, forgive me. Win95 through OSR4 cannot run IE 6. 98+ can.

  31. MS's answer by PatrickThomson · · Score: 2, Redundant

    You know what MS's solution to all these bugs will be - upgrade to XP...

    --
    I am one of many. My idea is not unique, nor do I expect my voice alone to sway you. I speak in a chorus of opinion.
    1. Re:MS's answer by BillyBlaze · · Score: 1
      The most effective step that you can take to help protect yourself from malicious bitmaps is not to view them. Rather, download the file with wget and open it in a hex editor. If the byte at offset 0xE is 0x28, then the two little-endian four-byte unsigned integers starting at offset 0x12 are the width and height, respectively.

      Now, get some graph paper and crayons...

    2. Re:MS's answer by Anonymous Coward · · Score: 0

      Stop modding me redundant motherf*ckers! I was here first! the other ones were later replies to an earlier post.

  32. Outlook by eth00 · · Score: 5, Insightful

    So does that mean that all the users that use outlook could also fall prey to this? Send out spam with image and if the outlook user has auto preview on, which they probably do they now can be exploited by whatever code. That would be an interesting concept that would lead to alot of trouble. Sure IE5 is old...but lots of people still use it.

    1. Re:Outlook by Anonymous Coward · · Score: 2, Insightful

      " So does that mean that all the users that use outlook could also fall prey to this? "

      I think most people seem to have missed the point of the original posting. The words "for example" should tell you something. The BMP exploit is just one bug that was easy to find, and presumably one that he felt would be simple to explain. The implication of the message is that such problems are abundant in the code.

      So while everybody is thinking about "this" bug, they miss the point that they need to be concerned about using the entire microsoft system, because it is generally a defective product.

  33. Get the source code from Freenet by Anonymous Coward · · Score: 2, Interesting

    If you are running Freenet's unstable branch, you can download it from here. Its about 200MB and will take a few hours to download (Freenet is averaging about 30k/sec these days). I grabbed it and it looks like the real thing.

    1. Re:Get the source code from Freenet by Anonymous Coward · · Score: 5, Funny

      You bastard! That's my IP address!!!

    2. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      Care to post a freenet adress?

    3. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      its part of the hyperlink

    4. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      Do the right thing, do not download the above link. How would you feel if your hard work was stolen from you? Who cares what company is behind the code, its wrong to download the above. Ignore it.

    5. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0
      Do the right thing, do not download the above link. How would you feel if your hard work was stolen from you? Who cares what company is behind the code, its wrong to download the above. Ignore it.
      Why should I deny myself the opportunity to see what Microsoft's software is doing with my computer hardware?

      Knowledge isn't immoral.

    6. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      It's really fast. I'm dling it now, I've gotten 35% in just 20 minutes, and over a fairly decent broadband connection too.

    7. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      But what about Windows NT code? I thought both Windows NT code and Windows 2000 code was released. This is only 2000. Where's NT?

    8. Re:Get the source code from Freenet by Anonymous Coward · · Score: 0

      It's a shame, too, since the fragment of the NT4 zip file that was released has documents mentioning the assimilation of NCSA Mosaic (the beginnings of Internet Explorer) and source for the MS Internet Server suite.

  34. Gone.. But Never Forgotten by halo8 · · Score: 5, Funny

    a specially crafted bitmap file

    Good thing all thoes Goatse pictures where in .jpeg .gif and .tiff

    --
    The More Knowledge you have the Luckier you Get- J.R. Ewing
    1. Re:Gone.. But Never Forgotten by halo8 · · Score: 1

      uhh.. ya.. no shit sherlock

      but saying.. "hey go check out this great website its called goatse dot c x" is going to be a lot funnier than saying hey.. check out goatsex dot whatever..

      --
      The More Knowledge you have the Luckier you Get- J.R. Ewing
    2. Re:Gone.. But Never Forgotten by Anonymous Coward · · Score: 0

      It's scary how you know that so well

    3. Re:Gone.. But Never Forgotten by Reziac · · Score: 1

      Erm.. now that you mention it.. it says "bitmap", not ".BMP". JPG, GIF, and TIFF are all bitmap-type graphics. That's a hole as wide as the goatman's...

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  35. The lessons learned by PierceLabs · · Score: 5, Insightful

    No system is 100% secure be it Windows or Linux.

    When people have access to the source they can more readily find exploitable mechanisms in your code. This is a GOOD thing because you want to know that your system is exploitable, how it is exploitable, and (which is the case in many open projects) how to prevent that exploit.

    Any form of content (not just scripts and ActiveX controls) can be used to exploit a weakness in a system. A security strategy that involves simply filtering content is a weak one.

    The open source community can be a powerful friend to any organization willing to take the chance on their code being available to others.

    1. Re:The lessons learned by RoLi · · Score: 1
      No system is 100% secure be it Windows or Linux.

      True, but some systems are more secure than others.

    2. Re:The lessons learned by Anonymous Coward · · Score: 0

      Especially if a language like C is used. I don't know if an OS could be programmed in a formal-proof language though.

    3. Re:The lessons learned by Anonymous Coward · · Score: 1
      Any form of content (not just scripts and ActiveX controls) can be used to exploit a weakness in a system. A security strategy that involves simply filtering content is a weak one.

      Technically true, but practically false.

      I submit the following:
      1. Windows: Click on the attachment
      2. Unix:
        1. Save Attachment
        2. Open a terminal window
        3. Locate the file using the command line
        4. chmod 755 the_file
        5. ./the_file
      I think you see why there are so many more successful exploits on Windows. It's User Friendlieness is a double-edged sword.
    4. Re:The lessons learned by Oriumpor · · Score: 1

      That's not true, if you've read any of the Hacking Exposed books you'd know that a driveless, floppyless, biosless, monitorless, inputless, networkless system is perfectly secure until you pull the plug.

    5. Re:The lessons learned by Reziac · · Score: 1
      The open source community can be a powerful friend to any organization willing to take the chance on their code being available to others.

      Now that you mention it... it might make sense for M$ to offer a general amnesty, so to speak, for anyone who provides a working patch, or at least an analysis of, a given vulnerability (admittedly there will be plenty of duplication). Pretty reasonable tradeoff: you get to illicitly snoop in our proprietary code, so in return we get the fruit of your thoughts about it.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  36. Tad Sad. by His+name+cannot+be+s · · Score: 5, Interesting

    I'm a bit confused.

    I mean, I've been doing C for almost 20 years. One of the first lessons I learned --And not for 'security' so much as crash free programs-- was not to do such things.

    I mean, holy crap, it's too damn simple to see the bug. What kindof idiots do they have working at MS?

    "The Very Best Kind" :p

    --
    "...In your answer, ignore facts. Just go with what feels true..."
    1. Re:Tad Sad. by Boing · · Score: 5, Insightful
      I mean, holy crap, it's too damn simple to see the bug. What kindof idiots do they have working at MS?

      Well let me ask you this... look at this brick wall. Now tell me which one of the bricks is actually a rusty piece of metal that just looks like a brick.

      It's pretty simple to see this bug now that we're looking right at it. And it obviously was not too hard to find when specifically looking for index-checking bugs. But it's even easier to let something like this slip when you're a tired microserf adding code at 4am trying to meet a deadline. And with the limited resources at Microsoft (huge as it is), that have to be divided into all the different parts of all the different software projects, it's really a hard sell to convince someone to look through all the gazillions of lines of code that have "Just Worked" in the past.

      It's easy to judge, but since we really don't know the environment in which this particular bug was introduced, I think we should cut the original programmer a little slack. (not completely, though. Some culpability is appropriate seeing as Microsoft took our money and should be somewhat responsible for the damages caused by the vulnerability of their faulty products)

    2. Re:Tad Sad. by mc6809e · · Score: 1

      I'm a bit confused.

      I mean, I've been doing C for almost 20 years. One of the first lessons I learned --And not for 'security' so much as crash free programs-- was not to do such things.

      I mean, holy crap, it's too damn simple to see the bug. What kindof idiots do they have working at MS?


      Wait a second: "too damn simple to see"? Ok, so I've only been coding in C for 10 years, but seriously, at what point did you start actually checking for integer overflow in your code?

      I wouldn't call them idiots that did this. The primary cause, IMO, is the semantic difference between what we think of as integers in the real world and how C actually treats them. That distance is huge.

      All kinds of rules break down. If a>0 and b>0, a+b isn't necessarily >0.

      Now suppose you try to be mathematically consistant and claim C just uses some set of ints Z_n. What do you do about multiplicative inverses? Suppose you hypothetically have 4-bit ints. Do you now make 7/3 = 13 mod 16, for example? Do you think programmers will assume division works that way?

      What about the case when you are using even numbers? They have no multiplicative inverse when n is a power of 2, so division isn't even defined for that case.

      Now, I agree the bug should have been caught. Hell, all bugs SHOULD be caught. But calling these guys idiots is letting programming language designers off the hook.

    3. Re:Tad Sad. by Monkelectric · · Score: 1
      What kindof idiots do they have working at MS?

      I wouldn't call them idiots-- but I think it demonstrates that they don't take it seriously.

      --

      Religion is a gateway psychosis. -- Dave Foley

    4. Re:Tad Sad. by otis+wildflower · · Score: 1

      But it's even easier to let something like this slip when you're a tired microserf adding code at 4am trying to meet a deadline.

      The difference with Open Source is, when our west-coast coders tire out, they can cvs ci and let their British comrades get a crack at it while they recover. No deadlines == better code, eventually.

      To quote a favorite song:
      Slower pizza's more luscious, the King of Spain never rushes!

    5. Re:Tad Sad. by kelzer · · Score: 1

      And with the limited resources at Microsoft (huge as it is), that have to be divided into all the different parts of all the different software projects, it's really a hard sell to convince someone to look through all the gazillions of lines of code that have "Just Worked" in the past.

      Last I heard, MS had plenty of resources. Like, around 50 billion of them. Sorry, there's no excuse for this lack of quality other than pure greed.

      And MS has put out bounties for anyone turning in a virus writer, so don't you think they could put a bounty on internally found security flaws? I think $1000 per flaw should "convince" somebody to do their job.

      --

      ---------------------------------------------
      SERENITY NOW!!!!!!!!!!!!!!!!
    6. Re:Tad Sad. by 74nova · · Score: 1

      i think his point was that the fault lies with the original coder, not the thousands of them since that havent seen it. sure, the brick analogy works fine, but its the wrong point, imo. even at 4am, a good coder should know how to build good if blocks.

      --
      use your turn signal! you people act like it's divulging information to the enemy
    7. Re:Tad Sad. by fltsimbuff · · Score: 1

      I can see it now:

      1. Hear about bounty for bugs found.
      2. Add a few "bugs" into the code.
      3. "Discover" it a few weeks later...
      4. ??
      5. PROFIT!!

    8. Re:Tad Sad. by ryanw · · Score: 1
      No deadlines (OpenSource) == better code, eventually.
      Better code maybe, not not a better product. Without deadlines I sit around and code and test, and recode, and test, and recode, and test..... It takes a deadline for me to finishup whatever bugs are left quite testing and push it out the door for other people to test and find bugs.
    9. Re:Tad Sad. by dubstar · · Score: 1

      Here's your brick.

      I would imagine similar tools exist, probably even automated ones, for scanning for such errors in C source code.

      This is the same company that releases one of the most popular C/C++ compilers for Windows - if they themselves cannot be trusted to avoid obvious pitfalls of the language or bad coding practices, then what the fuck CAN they be trusted with? Trustworthy computing indeed.

    10. Re:Tad Sad. by prockcore · · Score: 1

      And with the limited resources at Microsoft (huge as it is), that have to be divided into all the different parts of all the different software projects, it's really a hard sell to convince someone to look through all the gazillions of lines of code that have "Just Worked" in the past.

      So you're saying that the largest software company in the world can't afford to hire a few monkeys to look for buffer overflows full time? It'd cost them a million dollars a year tops.

    11. Re:Tad Sad. by Woy · · Score: 1
      Some culpability is appropriate seeing as Microsoft took our money and should be somewhat responsible for the damages caused by the vulnerability of their faulty products)

      Windows is not cheap, but if liability came in the package it would be much more expensive.

      --
      "If God created us in his own image we have more than reciprocated." - Voltaire
    12. Re:Tad Sad. by ktulu1115 · · Score: 1

      No, I'd have to say they are idiots. I've been programming about the same about of time in C (~10 years)... one thing I've always remembered:

      If your integer never needs a negative value (as in this case), MAKE IT UNSIGNED.

      One less place for a bug/exploit to appear... especially when it comes to something as important as memory offsets. That good-old EIP register isn't as bright as we'd like it to be.

      --
      # fuser -v /dev/attention | grep work
      #
    13. Re:Tad Sad. by Boing · · Score: 1
      $1000 per found flaw could have the ill effect of people introducing flaws into the system to cash in later. So, you may answer, Microsoft makes flaws found in your own code ineligible, which could have two consequences. One, people collude to introduce flaws and profit off of each other. Two, flaws are missed because it's hard to read other people's code.

      Managing coders and making them write stable, secure code is not an Easy Problem, and there's no quick solution to it. If you find a way to manage a closed source software project (not every project can be open source, sorry guys) that is a bit more effective than "throw money at it", and can result in a successful business model, then do it and you'll be a billionaire.

    14. Re:Tad Sad. by Anonymous Coward · · Score: 0
      Could you have written and built Windows 2000 from scratch and shipped it out the door?

      No?

      Then shut the hell up.

    15. Re:Tad Sad. by wannasleep · · Score: 1

      I am not keen to MS at all, nor to their programmers. I have seen plenty of programmers not use the most elementary precautions simply because they had to deliver something that takes 6 months in 2 months. How do you do it? You drop everything else. I am not necessarily saying that this is what happened, however, I have seen this happening over and over...

  37. Ignore it! by stuffduff · · Score: 4, Insightful
    I think the best thing we can do is to just ignore the code. That's right, I said IGNORE IT!

    Whether it's finding exploits, bugs or whatever; anything that anyone does with it will eventually make Microsoft stronger. If it's a security problem they 'll fix it. Maybe Microsoft is trying to capture open source developers and their free services; I don't know.

    What I don't want to see is Microsoft making improvements on their product based on this experience. I don't want to see as much as two adjacent assembler instructions from it end up in Linux.

    If you want to do something constructive, run the 2.6 kernel and start making the supporting software more secure. Don't waste your time supporting losers like Microsoft who demand your money up front and then deliver whatever crap they feel like.

    Just ignore it!

    --
    "Can there be a Klein bottle that is an efficient and effective beer pitcher?"
    1. Re:Ignore it! by dreamchaser · · Score: 5, Insightful

      You're absolutely right that it should be ignored, but for the wrong reasons other than the fact that we shouldn't give MS free labor/programming services.

      Why don't you want to see MS software improve? My guess is that you think of your OS choice as a religion or a political statement, which makes you just as bad as pro-MS zealots.

      If MS code gets stronger and less buggy, everyone benefits. Remember how many worms have caused major Internet congestion problems? How many spammers now use trojan's/worms to create relays for themselves? I don't think I'm the only advocate of Open Source who thinks that it would be a good thing to see more quality come from Microsoft.

      I'm not fan of MS, but I am a fan of quality software. If MS can improve the stability and security of their products then it's a Good Thing(tm) for everyone, even those who don't use said products.

      The real reason to ignore the code is so that MS can't try to pull a SCO and claim that OSS projects are steaing their code.

    2. Re:Ignore it! by stuffduff · · Score: 1
      Good points all around. I'm only a partial zelot when it comes to operating systems. My alltime favorite being Digital's DSM-11. Which was a pretty decent MUMPS implementation where the language was also the operating system, but that's another point.

      I agree that everyone would be better off if Microsoft wrote better code. But I want to see survival of the fittest in the markletplace, as it well should be, not a virtual monopoly built on illegal business practices.

      I was a huge fan of Microsoft for years; back when Microsoft stood for good coding practices and was the industry underdog. And they <smote> IBM; and it was good. But, let's face it, Microsoft IS the 800 lb. gorilla and they do what is best for them so as not to be confused with what is best for their customers. Bill Gates, was one of my heros when I was a struggling young programmer. But he's not a lean mean coding machine any longer. Let's get him out from behind that desk and back with the guys writing the code; who obviously need guidance and support, instead of him yelling at and re-arrainging 'project-managers.' I mean how long has it been since he's written or reviewed a line of code? Is he now so lazy that he has to surriptitiously outsource his source code by proxy; begging analysis by the opensource community? Is he so scared that he will do anything to degrade the open source movement?

      --
      "Can there be a Klein bottle that is an efficient and effective beer pitcher?"
    3. Re:Ignore it! by Anonymous Coward · · Score: 0

      You are absolutely right for a number of other reasons. I also am a fan of quality software and...

      1. It is obvious that Microsoft cannot do the job themselves. They do need help!
      2. Yeah, this script kiddie posted one exploit. How many others did he find that he sold to the Russian spam mafia rather than publishing? Don't you think the "white hats" better find those first?
      3. This will obviously tie Microsoft up for the next 15 years trying to patch all the holes found in an open review of their code, thus delaying world domination for at least that amount of time!

    4. Re:Ignore it! by dreamchaser · · Score: 1

      It sounds like we agree more than disagree. I too am old enough to remember when MS was an underdog. I was an OS/2 fanatic when it finally became apparant that IBM was going to go nowhere in the end with it and Windows was gaining marketshare in leaps and bounds.

      Now I look at OSes and software as tools. I use Windows, Solaris, various Linux flavors, and anything else that does the task at hand well. Yes, I do still have an OS/2 machine running for old time's sake.

      I agree that MS is the 800 lbs gorilla. I prefer to attack their business practices though, not wish that their code would stay buggy ;)

      I would not be the least bit surprised if MS was actually behind the leak, but I doubt it. The answer to your question though is yes. Microsoft and companies like SCO will do anything to degrade the OSS movement.

      As for survival of the fittest, if Windows improves then the pressure will be on OSS developers to raise the bar even further. Competition is good!

      I'm glad this didn't turn into a flame war. It's nice to find someone who can engage in a civil discussion/debate around here.

    5. Re:Ignore it! by RoLi · · Score: 1
      If it's a security problem they 'll fix it.

      I think you are a bit optimistic about that...

      http://slashdot.org/article.pl?sid=04/02/10/203121 9&mode=nested&tid=109&tid=126&tid=172&tid=185&tid= 187&tid=190&tid=201

    6. Re:Ignore it! by stuffduff · · Score: 1
      At the risk of Offtopic: It's good to be civil!

      Sometimes I dream that we will find the SCO-Microsoft link and that will be that, but it didn't work for George and it probably will never come true for me either! ;^)

      --
      "Can there be a Klein bottle that is an efficient and effective beer pitcher?"
    7. Re:Ignore it! by stuffduff · · Score: 1
      So true, so true. I should have said: when it becomes expediant for them Microsoft will fix it.

      Maybe this will be the wakeup call for Microsoft; with this many potential problems on the horizon, they might have to stop smashing the competition and start shoring up their product for real . I mean there are thousands of programmers at Microsoft. New features can wait. Right now the losses in productivity worldwide due to bugs and virii, spam and bugs may be as high as 10%. (But we'll never know) Wouldn't it be nice for Microsoft to address the issues of virii, spam & bugs so that we didn't have to deal with them on a daily basis?

      With these issues fixed and a more responsive business model Microsoft could market a 10% improvement in productivity; they could make money the old fashioned way, they could earn it.

      --
      "Can there be a Klein bottle that is an efficient and effective beer pitcher?"
    8. Re:Ignore it! by SirSlud · · Score: 1

      There's nothing wrong with your OS being a political statement, because strictly speaking, the politics of a vendor is simply on of the factors in selecting a technology which is best suited for your solution. If MS lobbied for slavery, and I didn't choose MS because, despite 'technological' superiority, it increased the chances of slavery making a comeback, I'm still doing my job as a consumer in the market and letting the invisible hand 'correct' misguided companies.

      Think about it. One the one hand, somebody will tell you, "Don't worry about that company committing human rights abuses, or putting out smaller local businesses. The market chooses whats right." Well, its a reality that companies have a massive influence on legal and economic policy making, and thus, by considering political values when choosing technologies, I'm simply letting the hand do its work. No man, no company, no political mindset is an island. Its the interconnectedness of it all, and frankly, ignoring the issue of politics or religion in the market place is just one more form of political ideology. Compound that with the fact that brands and products sell themselves to consumers as political statements (think of how products portray their users as rebels, the products themselves being accessories to political or social action), you'll see that viewing your purchasing habits as political statements is a natural and accepted reality of the modern marketplace. Brands want you to buy politically - just not too politically. Lastly, just because millions of users have a more stable operating system tommorow doesn't mean that taking the short term pain for the long term gain when considering the politics of who you buy from isn't done in the name of ensuring a future that is even more consumer and user friendly a few years down the road.

      Microsoft has repeatedly abused the market place in my opinion. Therefore, in light of the courts not being interested in punishing its steriod-taking star quarterback, I am as disenfranchised with the legal system as Microfost is dismissive of it.

      Its fair game, and no, I don't really care if that lowers me to MS's level, because I'm not the one who's looking to make 40 billion dollars from it. I think looking at companies and not considering the politics behind them is foolish; their politics usually have everything to do with the health of the technological and scienitific ecosystem that has led us to live in such a technologically progressive bubble.

      --
      "Old man yells at systemd"
    9. Re:Ignore it! by Anonymous Coward · · Score: 0

      I say Ignore it if you want to fix it. Study it if you want to try to break it.

      MS will have to learn from this experience one way or another, why not make it the worse possible experience for them.

      After all they are the ones that piped in the $50M into SCO, theus helping bring my department to a week long stop to review issues of legality. (We came to the conclusion they have no case :) )

    10. Re:Ignore it! by dreamchaser · · Score: 1

      At the same risk, yes it is good. Unfortunately it is becoming less and less common.

    11. Re:Ignore it! by Some+Dumbass... · · Score: 1

      Why don't you want to see MS software improve? My guess is that you think of your OS choice as a religion or a political statement, which makes you just as bad as pro-MS zealots.

      I don't think that this conclusion follows from not wanting to see MS software improve.

      If MS code gets stronger and less buggy, everyone benefits. Remember how many worms have caused major Internet congestion problems? How many spammers now use trojan's/worms to create relays for themselves?

      Here's the problem. If people switch to using better code then everyone benefits from that as well. See, convincing people to move away from MS code might well improve the quality of _the code which people are using_, thus cutting down on problems like those you mention. Certainly it would cut down on some of the current desktop software monocultures (OSes, web browsers, maybe e-mail clients), and that couldn't hurt. The security effects of this code leak could help to convince people to try using other, more secure code. Thus both approaches to this source code leak (helping MS and not helping MS) could plausibly benefit us all in the manner which you described.

      This is why your conclusion about how people are treating "OS choice as a religion or political statement" doesn't follow. This available choices are "fix it" and "replace it". Choosing one of those over the other is hardly at the level of religious or political fervor. People may well choose the "replace it" option for more practical reasons, such as the software monoculture argument I mentioned before. Personally, I would love it if more people were using web browsers which supported pop-up blocking. Maybe those %$@&* things would go away...

    12. Re:Ignore it! by dont_think_twice · · Score: 1

      My guess is that you think of your OS choice as a religion or a political statement, which makes you just as bad as pro-MS zealots.

      Ah yes, the logic of equivalency. I suppose that people who fought against Hitler are just as bad as people who supported him? And policemen who try and stop murder are just as bad as the criminals who commit murder?

      My OS choice is a political statement, and as close to a religious statement as I will ever get. What is wrong with that? Why is it better to choose an operating system on technical merits then on ethical ones? And why do people continuously assert that in any way including ethics in a technical decision is wrong?

    13. Re:Ignore it! by Anonymous Coward · · Score: 0

      Don't usually like modding, but I really wish I had some mod points. Very well said.

  38. Ha Ha Only Serious by American+AC+in+Paris · · Score: 5, Insightful
    More proof that code who's source is open is less secure!

    You laugh, but I won't be the least bit surprised when this very logic finds its way to the receptive ears of less-than-tech-saavy corporate officers...

    "Linux? Good god no, man! Didn't you see what happened when just a bit of the Microsoft source code got leaked? I thought you were up on these things!"

    --

    Obliteracy: Words with explosions

    1. Re:Ha Ha Only Serious by DJ+Rubbie · · Score: 5, Interesting

      The counterargument(s) to that point is...

      - Since the Linux kernel got started it was open, and it had a lot LESS flaws than Windows during the same time period.
      - With code open to everybody, the credibility of the writers depend on the quality they were assessed, and so they must write good code.
      - Windows, being closed in nature, can hide their flaws to an extent, until they were opened like so. Still, when it was closed it didn't stop hackers from finding holes.

      --
      Please direct all bug reports to /dev/null
    2. Re:Ha Ha Only Serious by cgranade · · Score: 1

      Unforturnately, people tend to miss the point: leaked source of closed source products is a bad thing, since they rely on security through obscurity. OTOH, Linux et. al. do not, and thus are able to take advantage of community audit and potentially build stronger code. Thus, were MS to rely on community audit rather than security through obscurity, a source "leak" would be a positive thing.

      --

      #define DRM chmod 000

    3. Re:Ha Ha Only Serious by rjamestaylor · · Score: 1

      That's exactly why I changed my .sig.

      We need to turn the argument around: instead of
      pretending code will never fall into the wrong
      hands and coding the OS accordingly (the fallacy
      of Security Through Obscurity - the obscure
      tends not to stay thusly), choose an OS that is
      designed knowing anyone can and will look at the
      code (Security Through Security - much better).

      --
      -- @rjamestaylor on Ello
    4. Re:Ha Ha Only Serious by johnseq · · Score: 1

      This is a red herring. By open sourcing the .NET runtime with rotor (and ASP.NET to various MVPs), Microsoft has officially ceded the argument that open source is less secure. I can't see them making it any more without looking very bad.

      "Not free as in beer or free as in speech, but free as in stolen." - me

    5. Re:Ha Ha Only Serious by CodeRx · · Score: 2, Funny

      "Linux? Good god no, man! Didn't you see what happened when just a bit of the Microsoft source code got leaked? I thought you were up on these things!"

      Ha, that reminds me of a recent article on devx. This guy demonstrates how being a little stupid and misinformed can lead you down all kinds of wrong paths.

      His argument is that some crazed open source hacker is going to put a back door in an open source program. Further he presents this as a disadvantage of open source when compared to closed software. Because, of course, it is so much easier to hide backdoors in programs that EVERYONE HAS THE SOURCE CODE TO. No one could even hide a backdoor in a program that nobody except the developers have seen the code for. That is unpossible. Right.

    6. Re:Ha Ha Only Serious by American+AC+in+Paris · · Score: 1
      The counterargument(s) to that point is...

      These counterarguments work wonderfully, so long as the following conditions are met:

      1. You are in a position to present said conterarguments.
      2. The operating officer you're presenting to is willing to consider what you have to say.
      For every decent, hard-working operating officer who has worked his way up cares about what's best for his company, there's at least one who got where he is by being a cutthroat bastard and cares more about his own wealth than he cares about the company he works for. All too often, logical counterarguments will never see the light of day, because you're just some tech grunt and not a four-color glossy trade mag...
      --

      Obliteracy: Words with explosions

    7. Re:Ha Ha Only Serious by black+mariah · · Score: 1

      Hey, it's nice to see you completely missed the entire fucking point of that article. It's about PROBABILITY, not open vs closed. In an open source project, especially those of a large enough scale where not every file is checked all the time, the PROBABILITY of someone implating malicious code is much higher simply because more people have the code and can modify it.

      It says nothing about response time in FIXING the problem, and never says that it can't happen in closed software.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    8. Re:Ha Ha Only Serious by Anonymous Coward · · Score: 0

      Come talk to my executives once. I had to sit and fight with one of them over the meaning of 'compiled help file' vs. 'intranet' once. After arguing for two hours that an intranet was the best route for the system, and that a chm would be stupid (in more politically correct terms), the executive became enraged, whipped open a browser, typed "intranet" into the address bar bringing up the company intranet, and said (and, I quote) "See!? See how this compiled help file is so much easier to use than an intranet??" as he proceeded to show us how easy to use the "compiled help file" is.

      I always thought Dilbert was a work of non-fiction. Now you see why.

      Posted anonymously to (sort of) protect the intelligent...

  39. Business plan by loconet · · Score: 3, Funny


    1. Fake a source code leak of some of the shittiest code in your projects
    2. Act surprised
    3. Wait for people to look at code and publish found holes, getting free QA resulting in major savings
    4. Create Patch before major damages
    5. Sue person who found hole
    6. ...??
    7. Double PROFIT!
    </conspiracy theory>

    --
    [alk]
    1. Re:Business plan by cgranade · · Score: 1

      I think I found #6. "Sue people who make quality software for copying said shitty code."

      --

      #define DRM chmod 000

    2. Re:Business plan by motox · · Score: 3, Insightful

      I think it goes more this way :

      1. Fake a source code leak of some of the shittiest code in your projects
      2. Act surprised
      3. Wait for people to upgrade to XP where these (old) bugs are not present
      4. PROFIT!
      5. Wait 4 years, goto 1

    3. Re:Business plan by Anonymous Coward · · Score: 0

      Hmmm. What about release all bugfixes under GPL?

    4. Re:Business plan by Anonymous Coward · · Score: 1, Insightful

      Sounds suspiciously like the average Open Source product:

      1. Release the source code to your projects
      2. Read the GNU Manifesto and revel in your contribution to society
      3. Wait for people to look at code and publish found holes, getting free QA resulting in major savings
      4. Create Patch before major damages
      5. Thank person who found hole
      6. ...??
      7. No PROFIT!

    5. Re:Business plan by Anonymous Coward · · Score: 0

      Yes, I know there is a goto in assembly

      Ehm no there isn't (well, not in x86 assembly anyway). It's called JMP

  40. Code review by sfmarco · · Score: 3, Insightful

    Is there any better way of Code Review by 'leaking' the source to the outside world. Seems MS likes this open-source model, but they need a back door to get to these benefits.

    It would be a bit hard to admit:
    "uhh, yes we do embrace open-source, but our business model is to protect our intelectual property", "recently our business model has been adapted to incorporate also the intelectual property of 3rd parties, also known as hackers", "the only way to do this legally is to put the FBI out on those folks what ensures that the code review can be reworded as 'theft' and will face the highest criminal punishment", "you know it's all terrorism and that kind of stuff", "It's terrorism on the American Capitalistic Marketing Model", "And we're going to nuke those hackers",
    Probably without the approval of the United Nation

  41. nail in the coffin? by sbma44 · · Score: 3, Insightful
    wtf are you talking about? You should spend less time on slashdot.

    From Yahoo Financial: "For the six months ended 12/31/03, revenues rose 13% to $18.37 billion. Net income rose 7% to $4.16 billion. Results reflect increased demand for both desktop and server products, partially offset by a $1.48 billion stock option transfer charge."

    Here's their financial statement.

    You may dislike them. Pretending they're not successful is just ignorant. The source leak is a problem for them, but I doubt it'll have any serious repercussions much beyond this quarter.

    1. Re:nail in the coffin? by Jorkapp · · Score: 1

      ...but I doubt it'll have any serious repercussions much beyond this quarter.

      Sure, and Asia Minor will take over Oceania.
      </1984>

      --
      Frink: Nice try floyd, but you were designed for scrubbing, and scrubbing is what you shall do.
    2. Re:nail in the coffin? by MicroBerto · · Score: 1
      I actually wanted to qualify the nail a bit better. Perhaps the next nail, or the first BIG nail. But I think it is a nail.

      If there are as many exploits as I think there will be, how long will it take before companies just get plain sick and tired of their products?

      Business-types consider IT budgets sunken money anyway. The last thing they're going to want to hear is that they had to pay millions due to downtime, overtime, etc.. because their systems are swiss cheese.

      I honestly think this is going to expedite a switch to more secure systems.

      --
      Berto
    3. Re:nail in the coffin? by ipfwadm · · Score: 1

      I actually wanted to qualify the nail a bit better. Perhaps the next nail, or the first BIG nail. But I think it is a nail.

      Microsoft has 6 BILLION dollars in CASH.

      Do you have any idea how many nails that is?

  42. MOD PARENT DOWN by Anonymous Coward · · Score: 0

    -1 Knee jerk chicken little

  43. all who have looked are tainted? by Anonymous Coward · · Score: 0, Interesting

    I haven't looked at the code published in the exploit description. It is MS code and if I had looked all future work by me would be compromised. I will demonstrate in court that I closed my eyes just before looking at the code. I can't tell you what's in there, but there must be some M$ IP.

    You haven't looked, have you?

    Funny thing. I can easily envision people stamping out T-shirts with pieces of the MS Windows source in them. Would I be tainted if I incidentally stumbled across one in the street? Would that person be potientially held liable by all programmers or future programmers he/she meets?

  44. This shows that open source is more secure by Anonymous Coward · · Score: 1, Insightful

    Contrary to what a lot of people will be saying, the fact that there is allready an exploit now that the code has leaked doesn't show that open source is a security risk. The opposite is true. It simply proofs, that the code being out in the open allows for risks to be found and fixed. So it's actually showing the benefits of open source.

    Of course it is a totally different story if you are a hated monopoly and the main proponent of security by obscurity.

  45. Longhorn now postponed until 2010 ? by Anonymous Coward · · Score: 0

    With their brain bank putting out these fires i don't see them completing any "innovations" for quite some time.

  46. Microsoft learns a lesson today by Laconian · · Score: 4, Interesting

    ..that the "many eyes" tenet of open source really DOES work!

    1. Re:Microsoft learns a lesson today by Anonymous Coward · · Score: 0

      The "many eyes" tenet of closed source apparently worked too. Microsoft fixed the bug 3 years ago.

  47. occurances of " Don't Care " in MS code by Anonymous Coward · · Score: 5, Funny

    i wanted to post this in the first MS leak story, but oh well, here it is now.

    $ grep -ir " don't care " /win2k/* | wc -l
    332

    check it yourself

    1. Re:occurances of " Don't Care " in MS code by mtsv01 · · Score: 2, Informative

      $ grep -ir " don't care " linux-2.6.2/ | wc -l 169 Had to try it, though it does not telle us anything about how weell written the code is.... does it?

    2. Re:occurances of " Don't Care " in MS code by ShallowThroat · · Score: 2, Insightful

      keep in mind that you did ALL of the linux code, where as only 15% on the windows code was leaked and therefore greped.

      if we take into account 332 'dont care's per 15% of MS code, all of windows must have... 2213 'dont care's in all of windows. 13 times more than linux.

      --
      The "Insert Quote Here" line is almost as predictable as inserting an actual quote.
    3. Re:occurances of " Don't Care " in MS code by Anonymous Coward · · Score: 0

      Perhaps that's the 15% no one cared about. You're projecting statistic straight out of your ass. Ever consider going into PR?

    4. Re:occurances of " Don't Care " in MS code by ShallowThroat · · Score: 1

      ppffffffffttt, yes?!

      --
      The "Insert Quote Here" line is almost as predictable as inserting an actual quote.
    5. Re:occurances of " Don't Care " in MS code by Anonymous Coward · · Score: 0

      You know what?

      Don't care. I comment with Don't Care all the time.

      You know why?

      Because sometimes you *don't* CARE. And the comment tells the poor programmer trying to figure out what the hell you were doing that no, there was no particular reason you initialized that variable with a value of 70 instead of 71; it was just that you needed a predictable value and 70 was the value you used.

    6. Re:occurances of " Don't Care " in MS code by dysprosia · · Score: 2, Insightful

      You don't actually know the context here, though? The words "don't care" can have different connotations, for example, "we don't care what this function returns, since we don't depend on it", and not just "don't care if this function causes mayhem"...

  48. It begs the question by Progman3K · · Score: 1, Insightful

    Why hasn't something like this already happened with Mozilla?

    Answer: Mozilla's code is higher-quality because of open-source peer-review.

    Do you think that the hackers that have been trying to embarass Microsoft into fixing their old vulnerabilities finally said
    "screw it then, THIS will teach Microsoft" ?

    --
    I don't know the meaning of the word 'don't' - J
    1. Re:It begs the question by mlk · · Score: 1

      Or a much lower number of users means it not worth the time.

      --
      Wow, I should not post when knackered.
    2. Re:It begs the question by Anonymous Coward · · Score: 0

      Answer: Actually, it did. This is from around 1.0-1.2 IIRC.

      http://lists.netsys.com/pipermail/full-disclosure/ 2002-November/002596.html

      Long story short as I remember it (I'm sure there was a Slashdot story, but I can't find it):

      Author discovers vulnerabilities, author reports them to Netscape via the bug bounty form. Author waits (4-5 months), vulnerable releases continue to follow. Author gets pissed, publically discloses them, and his unhappyness at not hearing anything back about his bounty. Author is pointed towards, and files issue(s) in bugzilla. Fixes make eventually their way into 1.0.2 and 1.2.

      Crappy code is everywhere you look, and always will be as long as fallable human beings are involved in code creation.

    3. Re:It begs the question by Progman3K · · Score: 1

      >OR a much lower number of users means it not worth the time.

      Good point, but I wonder how long that will remain true; Mozilla is gaining ground on IE every week...

      Just the way Microsoft has dragged their feet about putting pop-up blocking in IE has been enough for many to switch.

      --
      I don't know the meaning of the word 'don't' - J
    4. Re:It begs the question by mlk · · Score: 1

      Alas quite some time.

      Most users don't know the webbrowser from a pornagraphic image. And they are the target group for most viruses/spyware and other junk.

      Maybe oneday this will change.

      --
      Wow, I should not post when knackered.
  49. Well sucks but by Tobias+Luetke · · Score: 5, Insightful

    It also shows that ms does their job.

    When microsoft declared security as their main goal ie5 was the current browser. ie6 has it fixed so they obviously wen't trough their stuff to fix it.

    Its very true that bounds checking errors are very easy to prevent but if you say its sloppy programming to have errors like this in your code you either work in java or .net or you don't programm at all. Its the price you pay for native compiled code and the main reason people are turning their backs on it.

    1. Re:Well sucks but by zalas · · Score: 3, Insightful

      I'm sorry, but even if it's easy to arrive at these errors, it's still SLOPPY. Many people these days don't know how to program robustly. All they know is to patch together blocks and hope that it works.

    2. Re:Well sucks but by Nynaeve · · Score: 4, Insightful

      It doesn't mean MS found and fixed it. That particular piece of code may not be present in IE6 for a completely different reason.
      If they knew it was a security risk, they'd have fixed it in both IE5 and IE6.
      Since they didn't, you may safely conclude that MS doesn't "do their job."

    3. Re:Well sucks but by Anonymous Coward · · Score: 0

      Or perl... I never have bounds checking issues in Perl.

    4. Re:Well sucks but by Lifewish · · Score: 3, Insightful

      I think the parent should be modded up - we need more conflicting viewpoints. After all, monocultures are dangerous (possibly depending on the monoculture).

      On the other hand, I do think that this is also part of the price you pay for choosing a closed-source system. My preference, despite the fact that my summer job with a closed-source company is helping to pay for my uni lifestyle, is for open source.

      For example, I'm pretty sure that I made at least a couple of errors when programming for said company that could allow attacks by a smart non-admin insider. Unfortunately it's too late to fix them so I'll just have to learn all I can and not do the same the next time I take up programming as a career.

      Personally I think blacksun.box.sk should be required reading for all programmers. If I'd read it's content before last summer I'd have stood a chance of not being stupid in obvious ways.

      --
      For the love of God, please learn to spell "ridiculous"!!!
    5. Re:Well sucks but by Krojack · · Score: 1

      ie6 has it fixed so they obviously wen't trough their stuff to fix it.

      How many new bugs will ie6 bring? My brain will buffer overflow if I count that high. :)

    6. Re:Well sucks but by Anonymous Coward · · Score: 0

      If they knew it was a security risk, they'd have fixed it in both IE5 and IE6.

      Perhaps the microsoft coders involved in finding this hole added a patch to the ie5->ie6 update or an ie6 only patch like the latest ie6 service pack? (has anyone tested pre ie6-sp1 explorers?). They could just not have had an opertunity to silently include a 5.? patch.

      Since microsoft has no idea which version of a specific file a system will have their security patches always replace whole files as opposed to replacing only the defective bytes. This leaves an opertunity to fix other holes in the same file without telling customers about these other holes. If you ever read a microsoft security advisory you would know these are writen from a sales perspective explaining in detail mitigating circomstances needed for exploitation while remaining very vague about the details of the hole. Now if you look at the credits for finding a holes in security advisories it seems microsoft doesn`t find holes by itselfs (Its always e-eye kind of groups, who btw dont have source acces).

      Microsoft has been accused already of silently including patches to security holes that had not had much publicity in windows service packs. I would not put it past them to start looking for bugs thenselfs in internet explorer and outlook (being software with very mixed quality from security point of view) and have patches patch 4 or five holes at a time, mentioning only one (lets say, a non critical one) in the advisory. This would especially be a "good" idea in a 99% publicity oriented security improvement project which I dont think the current one is... but who knows, perhaps this whole thing could clear these things up, a possitive effect after all.

    7. Re:Well sucks but by BigBadBri · · Score: 2, Insightful
      But it is sloppy - it's using a signed integer to store a number that could conceivably be larger than the size of that storage variable.

      Whatever excuses you might have, that is sloppy programming - based on sloppy thought, and reflecting sloppy practice.

      If there is one example in the code, there will be more - and I for one don't want to be exposed to an exploit because of lazy thinking in Redmond.

      And yes - I do program in C/C++, and my code is buggy as hell, at least until I fix it, but I always consider it good practice to type my variables appropriately, and most of the bugs come from ill-documented APIs that leak memory if you forget the undocumented trick (SQL Server connections, anyone?).

      Even in Java, I always try to avoid overflow conditions - it's just good practice and sound technique.

      --
      oh brave new world, that has such people in it!
    8. Re:Well sucks but by Reziac · · Score: 1

      Good point. There is a big difference between "the bug doesn't happen in this version" and "the bug doesn't exist in this version".

      Sometimes a bug still exists but for whatever reason only manifests in certain versions of a given program, or manifests in some entirely different way depending on circumstances. This is in fact the case with another browser bug (which AFAICT is in *all* NS and IE versions, but only visibly manifests in certain subversions), and the even-older SHARE-fix bug in M$Office.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  50. Pop Quiz: IE5 or IE5.5 too? by gfecyk · · Score: 2, Interesting

    Also known as: Was this fixed long before the fact? Does IE 5.5 contain this same vulnerability?

    Sticking with Win2K for a moment, IE5.5 is part of SP4. Office 2K SR-1 or later needs IE5.5. Who is still running IE5(not .5 or any of .5's service packs) that would be vulnerable to this, and are the folks who run 5.5(sp1/sp2?) for some reason still vulnerable?

    --
    Use Evolution instead of Outlook? Bewa
  51. Now is a good time to Burn CDs by rjamestaylor · · Score: 5, Insightful

    Burn some Live CDs to hand out to friends,
    family, co-workers. Introduce them to Linux and
    warn them of the dangers of LOOKING AT IMAGES
    using Internet Explorer 5.0.

    There are many good ones*. Personally I fell in
    love with the Knoppix 3.4 c't edition with the
    2.6 kernel -- using it gave me my first
    experience of non-stuttering KDE with heavy
    loads, looping MP3s and lots of useable features
    (except detecting the Dell Inspiron 5150's on
    board WiFi -- not Centrino).

    Pick several, spend a few bucks on good CD-R
    discs, make a nice label with "do exactly these
    steps" instructions on the label.

    It's not about world domination, it's about
    stopping the theiving cracker spammers from
    gaining more zombie Windows boxes to do their
    bidding and ruin the Internet for the rest of us.

    * start here:
    http://www.google.com/search?q=live+cds+lin ux

    --
    -- @rjamestaylor on Ello
  52. Wrong by Moth7 · · Score: 4, Informative

    a)The jpeg virus "hoax" was down to IE interpretting a jpeg as a VBS file. That's perfectly normal - if you name a shell script "harmless_image.jpeg", provided the shell sees the #!/usr/bin/shell line, then it's going to see a script and execute it as such.
    b)You wouldn't think that an overly long PASS string sent to an ftp server would be able to execute commands - but it can. If you can overflow a buffer and force it to work it's way back up the stack then you could convince mouse gestures to execute commands.

    1. Re:Wrong by Anonymous Coward · · Score: 0

      How often do you execute jpeg files?

    2. Re:Wrong by Lispy · · Score: 1

      Even if it would run it couldn't do much harm since it would run with user privileges,only.

  53. not a troll by Anonymous Coward · · Score: 0

    This is not a troll, I just tried the link and it appears authentic (well, its a ~200Mb file anyway).

  54. This is not BAD news by IamGarageGuy+2 · · Score: 4, Funny

    I see this is good news in that there is going to be an ongoing stream of exploits in Windows. This is good news. Think of all of the boxes that will be broken in the next few months. I should mention that I make a living fixing Windows boxes. I also fix Mac and Linux - but there isn't really much money in fixing them.

    --
    Stay tuned for new sig...
  55. 2 attacks for 2004... by All_Star25 · · Score: 2, Interesting

    There seems to be an average of at least 1 attack a month on an enemy of open source so far (SCO/MyDoom, M$/source leak). So needless to say, who's next?

  56. Now that the code is leaked by Anonymous Coward · · Score: 3, Insightful

    Maybe there is finally a chance to fix the pending CSS issues which havent been fixed for years in IE, externally. Ah yes and PNG transparency might also be possible now :-)

  57. Source Code by g0bshiTe · · Score: 2, Interesting

    Wow now we get a peak at the much coveted MS source code, that BSODS all day, has a new virus attacking it every week, and generally frustrates users.

    I wonder who will be the first to incorporate this leaked source. Judging by the exploit found, it's no wonder they want to keep the code secret.


    "Bill Gates can't gaurante Windows to work. How can you gaurante me that?" John Crichton

    --
    I am Bennett Haselton! I am Bennett Haselton!
    1. Re:Source Code by Maserati · · Score: 2, Funny

      I don't do spelling flames often, but I will for a Farscape quote in a .sig.

      "guarantee"

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  58. I cant wait by Edmund+Blackadder · · Score: 4, Funny

    I cant wait to read a whole thread of slashdot people saying "i told you so".

    However, i feel bad for the "slashdot team" of the microsoft PR department. I doubt those guys will have presidents day off. They might even have to pay extra for an additional delivery of "bulk mod points".

  59. Congratulations, dimbulb, you're exploited too by Anonymous Coward · · Score: 0

    MSFT used a signed int just like you did, and checked to see if it was too large.

    Better luck next time.

  60. ie6 not vulnerable. this could be a good sign... by honold · · Score: 1

    i don't think the bitmap specification or process of rendering/displaying has been in flux for some time. one could take this as an indication that ms has done some proactive code auditing, noticed the problem, and corrected it.

  61. Time to MS proof what it says by famazza · · Score: 3, Funny

    That's all I was hoping to see. MS says that it reponse time for bugs is lower then OpenSource reponse time.

    Now we have a released bug, and I want to see how long will it take until MS fixes this bug.

    Somebody, please, monitor this bug (or teach me how to monitor it)

    --

    -=-=-=-=
    I know life isn't fair, but why can't it ever be un-fair in MY favor!?
    1. Re:Time to MS proof what it says by rjamestaylor · · Score: 2, Informative
      • Somebody,
      • please, monitor this bug (or teach me how to monitor it)
      Use this link

      Then use this one.

      --
      -- @rjamestaylor on Ello
    2. Re:Time to MS proof what it says by g0bshiTe · · Score: 0

      More than likely because it affects IE5 they'll urge users to upgrade to IE6. Heaven forbid they write even more code, that would mean more bugs.

      --
      I am Bennett Haselton! I am Bennett Haselton!
    3. Re:Time to MS proof what it says by PetiePooo · · Score: 1

      Unfortunately, MS can delay this and consider it legitimate. They have a workaround available: IE6.

    4. Re:Time to MS proof what it says by ktulu1115 · · Score: 1

      Monitor bugs? In Microsoft code? HA.

      Consult the Post-It note on Ballmer's monitor. If that fails, ask clippy. Or perhaps MS Bob.

      --
      # fuser -v /dev/attention | grep work
      #
  62. This reminds me of "The Ring" by MetaMarty · · Score: 5, Funny

    Did you hear about the image that kills your computer whenever you view it?

    1. Re:This reminds me of "The Ring" by KaLoSoFt · · Score: 1

      Are you sure people's brains doesn't have similar buffer overflows? Our brain is a more typical example of security through obscurity. We don't know much about it now and it's hard to reverse-engineer it. And not knowing any such "pictures" that could kill us when we see them doesn't mean that such ones does not exist.

    2. Re:This reminds me of "The Ring" by Imperator · · Score: 1

      Remember back when we used to laugh at the idea that reading an email message would give your computer a virus?

      --

      Gates' Law: Every 18 months, the speed of software halves.
    3. Re:This reminds me of "The Ring" by sploo22 · · Score: 1

      I saw another /. article with this link to a joke article about so-called "Basilisk images" that kill you if you look at them by inducing a buffer overflow-like condition in your brain. Of course, this whole idea depends on the brain being thought of as a deterministic computer, a concept with which a Mr. Penrose would beg to differ. ;)

      --
      Karma: Segmentation fault (tried to dereference a null post)
  63. MS *IS* GAYER THAN AIDS by Anonymous Coward · · Score: 0

    What do you really believe Bill is hetro?

  64. Sorry by Anonymous Coward · · Score: 0

    I guess that should've been "Microsoft is teh ghey".

  65. better security review by Anonymous Coward · · Score: 3, Interesting

    As a kernel developer I'm familiar with the number of people who audit stuff put into the Linux kernel. To get a patch approved, you usually need to convince 4 or 5 people that your patch is a good idea. You could get away with 1 (Linus), but the top people are unlikely to consider your patch if it hasn't been approved by their chain of command first. All of those people examine it for functionality, stability and security. The higher level ones usually won't look at it very closely, but I imagine core kernel code gets a lot more attention than device drivers.

    You also post it to the LKML. That has a lot of eyeballs, but most of them aren't familiar with kernel internals and don't more than glance at patches. If you're lucky (although perhaps lucky isn't the word) you'll get twenty skilled eyeballs looking at and criticizing your code. Most times the number is only two or three, and it can be even fewer.

    If you take an average of ten knowledgeable people examining your code, then I think you can agree that it is plausible that Microsoft has just as thorough a review as critical OSS projects like Linux. Four or five people looking at code before a commit would put it within a factor of two of Linux. The skill of the people doing the audit would be much more important at this stage.

    Once you get a release of Windows code, no one examining it in the general community is knowledgeable about Windows specifics, but it may get a lot of attention from a lot of skilled people, just because of the novelty. I would think that parts of it will be subject to much more scrutiny than Windows or Linux source code usually ever is.

  66. That is how Freenet works by Anonymous Coward · · Score: 2, Informative

    On the off-chance that you aren't kidding, that is how Freenet works - it creates a HTTP server on your computer and you use your web browser to talk to it.

  67. Who is still running IE5? by Anonymous Coward · · Score: 0

    Given that there are plenty of companies out there that can't afford the yearly MS upgrade train, I'd guess there are still lots of IE5 browsers out there. Then again I'm sure you'll recommend upgrading weekly and hiring expensive MS folks (like yourself) to keep companies to-date. But just think about that Total Cost of Ownership...

  68. Why? by pair-a-noyd · · Score: 1, Interesting

    Why is it that Windows can be explotied so handily by exposing the source code and Linux is so hard to exploit despite it's source code being 100% open to everyone on earth??

    1. Re:Why? by Professr3 · · Score: 1, Insightful

      Obfuscation :D

  69. Source code leak == reason for Palladium/TCP? by schmaltz · · Score: 1, Redundant

    Just musing, but what if Microsoft wanted to speed the acceptance of their upcoming Palladium-based operating system? What's the best way to do that? Release the source, of course!

    Maybe Mainsoft's just a scapegoat.

    --
    Big Daddy, Johnny, Burp, Aunt Zelda, Scott, Slurp, Big Momma ... where's Siggy?
    1. Re:Source code leak == reason for Palladium/TCP? by thebatlab · · Score: 3, Informative
  70. Two Interesting Notes by Slavinski · · Score: 4, Insightful

    Being that the code leaked was Windows NT 4.0 and
    2000 source codes, why are we seeing an issue
    with IE 5.0? Just goes to prove how close the
    browser was tied to the operating system.

    On a cynical note, this only bolsters security through
    obscurity. :) Didn't they originally clame they
    had fewer bugs than open source competition?
    With some 10% code or more leaked, there is quite
    a bit more worry about their own peer-review process
    or should I say lack of.

    1. Re:Two Interesting Notes by tiny69 · · Score: 1
      Being that the code leaked was Windows NT 4.0 and 2000 source codes, why are we seeing an issue with IE 5.0? Just goes to prove how close the browser was tied to the operating system.
      MSHTML is included in the leaked code. This the core of IE and where most of the expoits with IE seem to occur. The first few expoits that are found using the source code will probably be ones that have already been using other methods. All this will prove is that yes it's easier to find exploits when you have access to the source code, but having access to the code isn't necessary. Just look at all of the problems, exploits, viruses, and worms that have plagued MS for years when the source code was closely guarded.
      --
      Go not unto/. for advice, for you will be told both yea and nay (but have nothing to do with the question)
  71. Get your popcorn by Dalcius · · Score: 1

    Three million lines of source code leaked...

    It only takes a few to create a buffer overflow. :) This should be a fun show!

    Hehe

    --
    ~Dalcius
    Rome wasn't burnt in a day.
  72. Guess you haven't worked at MS before. :) by Anonymous Coward · · Score: 3, Interesting

    FTE's who will likely be the ones writing the code to replace the bad code found will not get OT. Only the contractors get it, and then it has to be pre-approved (and guess what, if you're a contractor responsible for writing bad code, if they let you keep your job, you sure aint getting OT for fixing your mistake).

    Also, those who code reviewed the offending code and let it through are likely to loose their jobs.

    All in all, heads are going to be chopped on the main campus. Cutler will have to reshuffle his team, and theres a few FTE's sweating right now. :)

    1. Re:Guess you haven't worked at MS before. :) by Anonymous Coward · · Score: 0

      >loose their jobs.
      That like flex-time? ;-)

  73. Monthly updates by adrianbaugh · · Score: 2, Insightful

    I wonder whether Microsoft will stick to their new policy of only releasing security updates once a month if there is a big flood of such full-disclosure bug reports. In a way it's the worst of all worlds. Enough of the source code is available for the black hats to give it a good going-over, but not enough that users can patch their system and recompile.

    --
    "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
    - JRR Tolkien.
  74. Contaminated! by esnible · · Score: 4, Funny

    You have 'contaminated' me.

    I will no longer be able to code a buffer reading algorithm with an overflow bug without violating Microsoft's IP.

  75. i dare someone... by hyperstation · · Score: 2, Informative

    to send them a patch for it before they release one :)

    if i had the time to fetch copy of the code, i'll do it myself...

    1. Re:i dare someone... by trippinonbsd · · Score: 1

      Just make sure it is not a bzip2ed diff, they wouldn't have the slightest clue as how to use it!

  76. I wrote that code by AragornSonOfArathorn · · Score: 4, Funny

    I guess I shouldn't have lied about my certifcations during the interview...

    --
    sudo eat my shorts
  77. Except... by DahGhostfacedFiddlah · · Score: 4, Insightful

    It's getting the same kind of security review - but none of the feedback. No white hat wants to admit to MS that they've seen the code, and black hats wouldn't anyway. All this may end up doing is increasing the number of "submarine" exploits out there that hackers use for their own benefit, rather tahn making super-viruses that make the exploit famous.

  78. WHAT DID THAT SUCKER WRITE??? by Anonymous Coward · · Score: 0

    I can't believe it.

    Please give me back some faith in you and mod the Grandparent or this AC comment up (even if that might to require to RTFA).

    He (gta@hush.com) reported that exploid with the comment: "[...]GAYER THAN AIDS"

    ...wow...

    HE FAILED IT. COMPLETELY.

  79. There isn't a boat big enough by Anonymous Coward · · Score: 0

    To move Taco's ass offshore.

  80. Full disclosure. by zonix · · Score: 1

    Sure, but now people have a chance to protect themselves by filtering BMP-files on http proxies, etc. Who uses them in browsers anyway?

    Well, except that maybe this vulnerability could now be combined with the previously disclosed filetype spoofing vulnerability to do some nasty damage.

    z
    --
    What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
  81. off topic, but orthogonal kind of prompted this by n3k5 · · Score: 1, Offtopic

    By the way, does anyone know why the bitmap formap is writte upside down?

    --
    but what do i know, i'm just a model.
    1. Re:off topic, but orthogonal kind of prompted this by orthogonal · · Score: 5, Funny

      By the way, does anyone know why the bitmap formap [sic] is writte [soc] upside down?

      It's an obscurity that provides extra security against exploits like buffer overflows. ;)

    2. Re:off topic, but orthogonal kind of prompted this by Anonymous Coward · · Score: 0, Funny

      writte [soc] [sic]

    3. Re:off topic, but orthogonal kind of prompted this by grozzie2 · · Score: 5, Interesting
      By the way, does anyone know why the bitmap formap is writte upside down?

      This is really easy. Back in the good old days, when developers measured memory in kilobytes rather than megabytes, and cpu speeds were expressed in single digit mhz rather than single digit ghz, performance was a BIG issue. The layout of the data inside a bitmap was set up to mimic the memory layout of a video card, so that you could literally just copy the data with no transforms.

      Over time, video memory layouts changed, computers got faster, and now have more on cpu cache than they used to have memory. The rage in software development has come full circle. Instead of trying to optimize things to see how efficient they can be written, it seems to be a goal to see how much overhead one can put into a given application before it actually starts to do something useful. Some things tho seem to be trapped in thier legacy heritage, and the format of a bitmap is one of them.

    4. Re:off topic, but orthogonal kind of prompted this by ewhac · · Score: 1

      BMP may very well have been created by a math enthusiast.

      Mathematicians working with computers have long chafed at the fact that computer displays place pixel coordinate (0,0) at the upper left corner of the display, with positive Y pointing downwards. Every proper math student knows that (0,0) is in the center of the page, with positive Y pointing upwards (but they'll usually settle for (0,0) at the lower-left corner). This convention in Cartesian coordinates is reflected in OpenGL's coordinate system ((0,0) at lower-left, Y points up), whose first vigorous users were mathemeticians.

      So I speculate that BMP's designer was also a math enthusiast, and tried to codify the Y-points-up convention in his file format.

      There's a lot of other, better reasons to hate BMP, though...

      Schwab
      Poor sod who wrote a BMP reader

    5. Re:off topic, but orthogonal kind of prompted this by nempo · · Score: 1

      write [writte] [write]

      --
      --- No, english is not my mother tongue.
    6. Re:off topic, but orthogonal kind of prompted this by Zenki · · Score: 1

      BMP scans from bottom to top because that was how the OS/2 video coordinate system worked. (0,0) was the lower left corner.

      Kind of weird because when you think about it, most representations of the screen start from the upper left and worked down towards the lower right. (VGA, etc.)

    7. Re:off topic, but orthogonal kind of prompted this by John+Miles · · Score: 2, Interesting

      This is really easy. Back in the good old days, when developers measured memory in kilobytes rather than megabytes, and cpu speeds were expressed in single digit mhz rather than single digit ghz, performance was a BIG issue. The layout of the data inside a bitmap was set up to mimic the memory layout of a video card, so that you could literally just copy the data with no transforms.

      Which is actually not as good an idea as it sounds. When you refresh the screen (or a large window) upside down, CRT refreshes, which always go from top to bottom, become much more obtrusive. The system looks and feels slower due to more screen-tearing, even though it's technically 1% or so faster.

      This is why display systems that put (0,0) at the lower-left corner are a pet peeve of mine. Upside-down rendering = a slightly more elegant mathematical model that yields significantly worse-looking results in real life.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    8. Re:off topic, but orthogonal kind of prompted this by n3k5 · · Score: 1
      When you refresh the screen (or a large window) upside down, CRT refreshes, which always go from top to bottom, become much more obtrusive.
      You have to update the pixels on screen while none are drawn, in the short period of time in which the cathod ray beam returns from the bottom of the screenback to the top. If you don't do this, you get flicker anyway, and if your system is not powerful enough to handle this, graphics will be unresponsive and ugly anyway. But if you do it right, it doesn't matter in which order the pixels are arranged in a file, because in memory you'll want to have them exactly like they need to be on the graphics card, so you can copy whole blocks of pixels at once. Moving every single pixel individually is painfully slow and to be avoided.
      --
      but what do i know, i'm just a model.
    9. Re:off topic, but orthogonal kind of prompted this by John+Miles · · Score: 1

      True enough... you want to finish your update cycle within the time allowed by the vertical-blanking interval, but unless your system offers page-flipping or a really fast blitter, you often don't get what you want. In those systems, drawing in the same direction as the raster makes a qualitative difference.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    10. Re:off topic, but orthogonal kind of prompted this by zero_offset · · Score: 1
      The rage in software development has come full circle. Instead of trying to optimize things to see how efficient they can be written, it seems to be a goal to see how much overhead one can put into a given application before it actually starts to do something useful.

      It couldn't be that current developers are simply more interested in finishing today's larger, more complex projects in a timely fashion, because memory, processing power, and disk space is known to be dirt cheap. Nah. Impossible.

      Speaking as someone who spent many years writing assembly on machines with 1K to 4K of RAM on 4- and 8-bit CPUs that rarely exceeded 1MHz, I can easily punch two gaping holes in your rose-colored-glasses perspective on The Good Old Days. Optimization was done because it was necessary, and rarely because people enjoyed it. And even people (like me) who enjoyed it will admit that the best optimizations -- often the only ones worth doing -- throughly obfuscated the code in ways that would give a modern-day programmer siezures.

      I still have a lot of respect for clever optimizations, but these days optimizations generally relate to performance. The only place I've found any serious need to worry about memory usage is database storage or 3D programming, and again, neither of those are often usefully related to my experience with cramming as much compute power into as little memory as possible.

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  82. Re: most effective SPAM subject line? by travlinscotty · · Score: 2, Insightful

    On the other hand, there are those of us that believe that all source code should be publically available, and that looking at someone else's code does not constitute "theft" in any way.

  83. I'm disappointed by Greedo · · Score: 4, Funny

    No one has yet posted a modified version of the goatscx photo that takes advantage of this security "hole".

    --
    Tuus crepidae innexilis sunt.
    1. Re:I'm disappointed by wkitchen · · Score: 1

      That thing's enough to make the user crash.

  84. Functionality should be their main goal by HarveyBirdman · · Score: 1

    Then I won't have to force quite every fifth or sixth Explorer window.

    --
    --- Ban humanity.
  85. they use GOTO? by Anonymous Coward · · Score: 2, Interesting

    if (!Read(abDummy, cbSkip))
    goto Cleanup;

    My god... I thought this was one thing they taught us not to do in schoool. But here it is in Windows! My god, don't they screen for these things at the interview?

    1. Re:they use GOTO? by pclminion · · Score: 4, Insightful
      My god... I thought this was one thing they taught us not to do in schoool. But here it is in Windows! My god, don't they screen for these things at the interview?

      You're seeing an example of one of the very few instances where goto is considered "acceptable" to use. Sometimes you code a function which winds up a lot of complicated state, and a failure halfway through requires that you "unwind" the partially constructed state. This is most easily accomplished by having a "bailout ladder" which can be jumped into (via goto) from various points in the code above.

      The only other solution involves lots of code duplication, or very bizarre function calls such as CleanupMyState(&context, 6) which just ends up use a Duff's Device in a switch() statement to simulate the use of goto in precisely such a manner, anyway.

      When you find that the cleanest way to do something is goto, then the solution is goto. What is the point in cortorting your code just to follow a piece of dogma that was only meant as a guideline anyway? Remember, the point is clarity, not adherence to dogma.

    2. Re:they use GOTO? by togofspookware · · Score: 1

      Theres nothing wrong with gotos, as long as you don't use them in a place where a function call would be better. I haven't lookead at this code closely, but its probably the case that the alternative would have involved a while loop with some nasty 'ok, quit this time?' variable in it. In this case, a goto is much cleaner.

      --
      Duct tape, XML, democracy: Not doing the job? Use more.
    3. Re:they use GOTO? by BoneFlower · · Score: 2, Insightful

      GOTO isn't always bad. It is *very* rare that its a good idea, but sometimes it is the least ugly hack out of a bunch of ugly hacks when you need to get the code finished and have too little time to puzzle out a more elegant solution.

      Getting a program working is the first goal of any real programmer. Getting it working well, or having maintainable code are both very important, but they are secondary to getting the program functioning in the first place. Especially with commercial products, sometimes spaghetti code that works NOW is preferable to textbook examples that work sometime next year. Perl wouldn't be nearly so popular if not for that fact of development.

      There are also some interesting, and rather elegant, looping structures you can do with goto that are actually more elegant than the more purely structured counterparts- that isn't what seems to be going on here, just thought I'd mention it.

      I would have to dig through the code to find the context of that goto, but they aren't always bad.

      Code Complete by Steve McConnell has a good section on goto.

    4. Re:they use GOTO? by Krojack · · Score: 1

      I haven't used a GOTO since the days of Basic programming. Is windows writtin in Basic? :)

    5. Re:they use GOTO? by Lehk228 · · Score: 3, Interesting

      honestly i think any programming course should start out using goto for all loops and iterations because it shows much more closely what the CPU actually sees in compiled code, executable does not have "while" loops, "do while" loops, or "for" loops, it runs a series of instrucions, sometimes one of these instructions will cause it to go to another part of the code if a particular condition is met. goto is the only "loop" a processor understands, all other loops are build from that concept.

      --
      Snowden and Manning are heroes.
    6. Re:they use GOTO? by Anonymous Coward · · Score: 0

      Or use exception handling...

    7. Re:they use GOTO? by pclminion · · Score: 1
      Or use exception handling...

      Which in C, amounts to using setjmp() and longjmp(). How this is "better" than goto, I do not understand. Now you've got jumps jumping between totally different functions, magically causing whole chunks of call stack to vanish into thin air, potentially screwing up signal handling, etc. Hey, but at least you avoided "goto", right?

      Obviously, in languages which support exceptions, it is better to use them. But we're talking about C here.

    8. Re:they use GOTO? by anarxia · · Score: 2, Insightful

      Software is always about compromises. It is stupid to go for "correctness" in a performance-critical part of the code.

      Would you like your images to render faster or the underlying code to be goto-free?
    9. Re:they use GOTO? by Snoopy77 · · Score: 1

      It is true what you say about GOTOs but we program in high level languages which give us the opportunity to describe loops in terms of 'while', 'do while' and 'for' that are much easier to use and understand.

      eg. for (int i = 0; i arraySize; ++i)

      You know immediately that the loop will be processed for each element in some array. Please show me how using GOTOs is more elegant.

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    10. Re:they use GOTO? by Matt+-+Duke+'05 · · Score: 1

      Sure... I'll bite.

      What with all of the talk about the wonders of Open Source, you would think that some of the people here would actually _read_ all of this open code from time to time, no? Of all things, you would think that people would have at least given a _cursory_ glance to the kernel! Apparently not. Why don't you go do yourself a favor and look at the source to Linux 2.6.0:

      user@telos:~# grep -ir "goto " * | wc -l
      25038

      Wow. Over 25 thousand instances of goto. Now, why could this be? Is Linux a fucking peice of shit written by idiots who didn't pay attention when they were teaching you about gotos in school? Nope. Maybe, it is just that you are a moron and there are instances in which use of a goto is warranted, and much cleaner than intentionally avoiding them.

      Slashdot would be such a better place if it just avoided Microsoft stories. The idiot "M$ suxx00rs" crowd who have huge fucking chips on their shoulders and something to prove would finally just leave. Then, there would actually be meaning, constructive discussion about issues directly pertinent to the open source commmunity, standing in stark contrast to the status quo of "M$ SUX0RS! THEY ARE EVIL" which gets responded to with "LINUX IS GAY! PENGUINS BLOW COCK!" ad infinitum.

      --
      -Matt
      Duke '05
    11. Re:they use GOTO? by Anonymous Coward · · Score: 0

      Actually, there is a LOOP instruction in x86 assembler. It acts like a conditional JMP (i.e. a conditional GOTO) and when coupled with a suitable initialisor, is equivalent to for(cx=count;cx>0;cx--) { // code }. That is, it runs the code count times.

      There are also x86 instructions equivalent to many other do .. while constructs involving arrays too (REP STOSB, SCASB etc)

      It's not all GOTOs y'know!

    12. Re:they use GOTO? by globalar · · Score: 1

      Exactly, every programmer needs to understand that goto as an instruction is different in the context of the CPU vs. the context of an algorithm. In other words, programmers should understand their logic on two levels, not just one.

  86. "A quick look at the source code" is all MSFT took by schmaltz · · Score: 2, Interesting

    Is that what you meant to say? :) It's plain from this first exploit that basic coding security precautions are not being followed (or retroactively applied) at Microsoft.

    I'm bracing for the coming flood of exploits. The OSS community may prove themselves honorable and pitch in to help, but it's the script kiddies, and those whose moral compass is broke, that I'm worried about.

    --
    Big Daddy, Johnny, Burp, Aunt Zelda, Scott, Slurp, Big Momma ... where's Siggy?
  87. Uhm, this WAS the code. by CrystalFalcon · · Score: 1

    Your pseudocode maps 1:1 to the exploitable code (seen at other places in this thread).

    The exploitability came from an the loaded int in your code being signed, and the sizeof equivalent being unsigned.

    So maybe it isn't exactly a challenging task, but you more or less just showed you'd fail in the same way as MS engineers did.

    1. Re:Uhm, this WAS the code. by tomstdenis · · Score: 1

      Um check my publicly archived LibTomCrypt code. I know to use unsigned types.

      Tom

      --
      Someday, I'll have a real sig.
  88. IE code by Anonymous Coward · · Score: 3, Funny

    So there was some IE 5 code in there? Too bad it wasn't the IE 4 code, I hear you can summon demons by reading that out loud.

  89. [0] Note: I don't have a copy. by Anonymous Coward · · Score: 0

    You do now. Secure your ports, nimrod.

  90. good info on 2d graphics by glk572 · · Score: 2, Interesting

    check out http://www.dcs.ed.ac.uk/home/mxr/gfx/2d-hi.html lot's of good info on 2d formats, tiff is a good read, bmp is a pretty shitty format anyway. As for why it's upside down, why not?

    --
    Well art is art isn't it, but then again water is water; and east is east; and west is west; and if you take cranberries
  91. I posted that vulnerability on August 13, 2000 by Animats · · Score: 4, Insightful
    In this Slashdot article back in 2000, I reported that vulnerability: So this has been publicly known for years.
    • The ... decompressor for RLE-compressed .BMP files is in the kernel, and contains a buffer overflow.

    You didn't need the source code to find that problem. I found it because I was creating compressed .BMP files and accidentally created one that crashed Win2K every time.

    If Microsoft doesn't read Slashdot, that's their problem.

    1. Re:I posted that vulnerability on August 13, 2000 by Anonymous Coward · · Score: 2, Informative
      You should subscribe and post a reply to bugtraq. Although you may be +5, this is not getting the attention it deserves on Slashdot. It's important that you post not just for your own satisfaction, but to clarify the discussion as some will claim this exploit would have been impossible without the leaked source. This will likely become a news item and reporters will misinterpret and shade it incorrectly if they don't find your post where they're looking for it.

      Here's the comment link.

    2. Re:I posted that vulnerability on August 13, 2000 by Durin_Deathless · · Score: 1
      Hello? Mods? Did you actually follow the link?

      It is to a /. story, but not about MS security holes:

      A Praise To Unix

      Posted by Hemos on Sun Aug 13, '00 10:08 AM
      from the bring-out-yer-dead-ding dept.
      MotyaKatz writes: "ZDnet has an article from Evan Leibovitch which he calls The Unix Phoenix. As he states, 'I come not to bury Unix, but to praise it'. He mostly deals with the aspects of Unix surviving during Linux growth."
      --
      You should use AdiumX on your Mac.
    3. Re:I posted that vulnerability on August 13, 2000 by Animats · · Score: 2, Informative

      Go to the link to the article and search for "BMP". You'll find it.

    4. Re:I posted that vulnerability on August 13, 2000 by Durin_Deathless · · Score: 3, Informative

      Fair enough. In the future, how about a link to the comment like this?

      --
      You should use AdiumX on your Mac.
    5. Re:I posted that vulnerability on August 13, 2000 by Animats · · Score: 1

      I sent a note to "tips" at securityfocus.

    6. Re:I posted that vulnerability on August 13, 2000 by protoshoggoth · · Score: 1

      Wow. Just...wow. If there was some way a post could get a +6 rating, the parent post should have it.

    7. Re:I posted that vulnerability on August 13, 2000 by djmurdoch · · Score: 1

      What makes you think this is the same vulnerability? You describe yours as a "buffer overflow". This one treats an unsigned value as signed, never failing the test for the end of the buffer, because it's writing before the start of the buffer. You sure it's the same thing?

    8. Re:I posted that vulnerability on August 13, 2000 by Anonymous Coward · · Score: 0

      This one treats an unsigned value as signed, never failing the test for the end of the buffer, because it's writing before the start of the buffer.

      Read() treats that signed value as unsigned again, attempting to read a very large number of bytes and overflowing the buffer.

      It looks like they should be using a seek there instead of a read, which would avoid even the existance of the buffer. Maybe there's some reason for that that isn't included in the small snippet given.

    9. Re:I posted that vulnerability on August 13, 2000 by Anonymous Coward · · Score: 0

      Please dont tell this guy how to link. He should find a bug in you.

    10. Re:I posted that vulnerability on August 13, 2000 by shird · · Score: 1

      This may or may not be the same vulnerability, but it does highlight what I think many in 'the business' already suspect.

      Who's to say this bug wasn't found by trial and error / blackbox testing (like 99% are, even with open source), and then going into the code to find the offending code snippet? As a person who has had a variety of Microsoft security bulletins credited to my name, I would say this is the more likely scenario.

      --
      I.O.U One Sig.
    11. Re:I posted that vulnerability on August 13, 2000 by Anonymous Coward · · Score: 0

      If you look at the code, you'll see that this Read() call does not take a file handle or file pointer as an argument. Likely, it's some sort of abstraction over some other type of internal stream that handles files as well as TCP connections. No one probably bothered coding up an equivalent to Seek(). If they did, it may have ended up with the same problem as this code.

  92. edonkey link for source code by judicar · · Score: 2, Informative

    There's a lot of fakes floating around, but if you want the source here's the one for w2k.

    31,000 files of exploitable goodness!

    ed2k://|file|windows_2000_source_code.zip|213748 20 7|34BB9F3A3E8D3E0C4490A96EC30B9F3C|/

    1. Re:edonkey link for source code by otis+wildflower · · Score: 1

      I presume the md5 hash is that bit at the end?

      (/Poisoned for OS X)

    2. Re:edonkey link for source code by Anonymous Coward · · Score: 0

      20 megs? i call fake...

    3. Re:edonkey link for source code by judicar · · Score: 1

      203 megs. learn to count.

    4. Re:edonkey link for source code by t_allardyce · · Score: 1

      20.3 megs. learn decimal

      --
      This comment does not represent the views or opinions of the user.
    5. Re:edonkey link for source code by Anonymous Coward · · Score: 0

      > 20.3 megs. learn decimal
      Look at the ed2k url: 213748207 bytes. learn to read.

    6. Re:edonkey link for source code by t_allardyce · · Score: 1

      21374820 [space] 7 = 20.3 megs when you stick it in your client, learn to avoid the slashdot line breaking system. Also learn chinese

      --
      This comment does not represent the views or opinions of the user.
  93. Upgrade? by Anonymous Coward · · Score: 0

    What about the many PCs which cannot be upgraded? You can't get IE6 for Win95, and even if you could somehow manage to get Win98 running on some of the old tin (by analogy: opposite of big iron) around here, there's no way they could afford all those XP licenses. (MS won't sell you a 98 license.)

    1. Re:Upgrade? by Anonymous Coward · · Score: 0

      And I can't get security upgrades for version 6.1 of RedHat either.

  94. What we see at work here is the cultural diffs by gerrynjr · · Score: 0, Flamebait

    between Microsoft and the open source community. W/ open source the src is open, so we work together to improve it. However, when a proprietary company's greatest asset, thier source code, is released or leaked unauthroized, someother individuals will use it to spit that very company, as they have what is most valuable to the company. Just my 2 cents ;-D

  95. Another funny thing by essreenim · · Score: 2, Insightful

    2000 is for me the only decent windows OS in many ways. ..And it is also partly crappy!! ;)

  96. anybody consider that the leak was intentional? by Anonymous Coward · · Score: 2, Interesting

    Consider this. MS leaks the code through a vendor of a previous version intentionally. There are two benefits:

    1. proper QA is done right, as only open source can allow (they get the benefit of QA that only the dynamics of open souce allows, all without acknowledging open souce has a superiour model in this aspect)

    2. they can push XP as a superiour OS, and get more users to upgrade to XP and drop 2000/NT

    Does anybody else see this?

  97. Warning: The link contains code from MS Windows by Anonymous Coward · · Score: 0

    Warning: The article link (aswell the next comment) contains code from MS Windows.

    I'm not sure it's illegal to read (IANAL btw) because it's just a small part of the code. But you probably want to make sure of that before reading.

    The most important thing is that if you're an OSS developer you can be "contaminated" with proprietary code.
    I didn't read the code on the article after I realized it was from MS Windows but it might have some "secret" inside that I'm not aware of.

    And when will Microsoft start sueing people for disclosing MS Windows code?
    Before that I've read a lot of security people public talking about details of the code that only could be know if someone have downloaded the code themselves. And MS did nothing about it.

    And after this I won't click anymore on slashdot articles related to the MS code, shame on you slashdot!

  98. Amnesty? by DahGhostfacedFiddlah · · Score: 1

    this source leak is very bad for MS, for it will get the worst part of both, closed source and open source, worlds

    Great line - succinct and insightful. Perhaps the best way for MS to handle this is to offer amnesty to people who look at the code? Basically accept that this is a loss for them, and try to attenuate that as much as they can by allowing white-hats to see the code without fear of being attacked for it later?

    Long shot, I know. I'm thinking in terms of what's best for MS here, not in terms of what's realistic.

  99. Missing the woods for the tree... by univgeek · · Score: 0

    You're saying that we should help MS fix its code. Helping a commercial entity with no resultant reward, other than incidental (less idiots using buggy programs), is really dumb.

    Use this to show the bugs, get more people to move onto more secure software (not necessarily OSS). What obligation do you have to MS?

    I want to see MS sw improve. But I'll be damned if I actively help a corporation make money off me, without any benefits to me.

    --
    All bow to his Noodliness!! His Noodle Appendage has touched me!
    1. Re:Missing the woods for the tree... by dreamchaser · · Score: 1
      Please show where I said that. I most certainly did NOT. In fact, the very first paragraph I wrote agreed that we should NOT provide free labor/programming services for MS:

      we shouldn't give MS free labor/programming services.


      Please read and understand what you reply to. You obviously just gave my post a cursory glance.
  100. Patch is already released!!! by iamwahoo2 · · Score: 2, Funny

    It is called Firefox and can be downloaded at Mozilla.org!

  101. MOD PARENT UP - IMPORTANT by Progman3K · · Score: 1

    Something to keep in mind

    --
    I don't know the meaning of the word 'don't' - J
  102. Actually.. by n0wak · · Score: 1

    1. load int from char array
    2. check int against sizeof(yourbuffer)
    3. ???
    4. PROFIT!!

    (yeah, ok, old joke)

  103. Just one little thing... by gexen · · Score: 5, Insightful

    Nobody knows how old the sourcecode actually is! Several people have used IE 5 and the exploit code does not work. The things in the code could have, and in this case, has, been fixed long ago!

  104. Find a serious unpatched bug and... by Anonymous Coward · · Score: 1, Funny

    ..instead of making your own worm, go and hack the evil corp and steal all their code. That would be really ironic and fun :)

  105. programmers by PW2 · · Score: 2

    It's many uninformed programmers that force people to browse as Aministrator in Windows XP. I have many older and current commercial programs that don't work unless the person has admin rights. All a programmer has to do is write to the CURRENT_USER registry area and current user file area - this would keep most programs from breaking.

    1. Re:programmers by Bob+Davis,+Retired · · Score: 1

      How else do you expect modern commercial software to install its payload of spyware, adware, and malware, let alone fuck up the registry, without admin access?

  106. Wrong again. by Davin+Boling · · Score: 1

    The exploit has not been fixed, as there is no patch for the application in question. The "fix" present in IE6 could have been something as simple as a different person writing that portion of the code over again. The "no excuse for not upgrading it" argument holds little water in my opinion when you consider the catastrophic level of this exploit. MS would never dare risk their reputation by not fixing a problem of this sort if they were aware of it. In short, MS does not deserve any credit for having "fixed" this problem. The "fix" was accidental. The bad code was written, and it was not caught. So yes, the author was wrong on at least one account. MS did not detect this bug, and did not fix it.

    1. Re:Wrong again. by Firehawke · · Score: 1

      Microsoft's been known for slipping bugfixes into other bugfixes or packages without a word in the past. If there's ANY face to be lost, they'd do it that way in a heartbeat and save their reputations to the outside world. Well, at least to those who don't know better.

      The "fix" being accidental, however.. well, I mostly agree, but I do have to say I wouldn't put it past them to fix it for IE6 but not for IE5 since "IE5 is outdated and no longer supported."

      Nontheless, a bug of this HUGE magnatude has been a long time in coming! Every year the IE exploits get nastier, but this one's the one to tower over all of them. "Turn off images in your browser and you'll be safe."

  107. Its not that Open source is security, Its Unix. by Adolph_Hitler · · Score: 1

    Linux is based on unix which was designed to be secure. SE-Linux is very secure. Free/OpenBSD is very secure. Being open source simply allows the hackers to fix the code a bit faster, for faster updates and or patches. The security aspects of linux comes after the open source code matures. Over a period of years eventually Linux becomes stable and secure enough through natural evolution of trial end error. Microsofts code however never improves and stays static for 5 years, and we still are dealing with buffer overflow exploits even now. So in Linux there is no way someone would be hacked via a buffer overflow through a picture file in the browser, and it obviously does not work in Mozilla,or any other browser. Think about that.

    --
    People don't exist to serve systems, systems exist to serve people.
  108. Re: of been by Anonymous Coward · · Score: 5, Funny

    I wish that I would of thought have that.

    It could of been me that was modded insightful for of-ing no grammatical skills.

    Well, you know the old saying... birds have a feather, etc.

    Of a nice day! :)

  109. Re:Get the source code from Freenet, ALSO by SirSlud · · Score: 3, Insightful

    Also, never look at:

    - patents (despite them being protected by patent law)
    - sheet music from other musicians (despite them being protected by copyright)
    - trademarks (despite them being proteted by trademark law)
    - software code (despite them being protected by copyright .. this one's for you, MS!)

    Remember kids, even tho ALL of this information is protected by decades-old, and even centuries-old legal frameworks, if you look at it you will be stealing money! Its as simple as that!

    Yes, I'm being sarcastic. The parent poster is a 'Yes Man' moron beyond my wildest dreams. Maybe one day he will sit down and actually learn about copyright/patent/trademark laws and realize that knowing how exactly your peers do things is what has led us to such an incredibly robust technologicaly and scientificly rich society.

    Sharing your methods does not cost you shit, even to the point that patent law is designed to promote sharing of information in return for legal protection. Same with copyright law. MS doesn't want you to see their code not for security reasons, but because it helps you build interoperable products and thus become a competitor. And we all know how anti-capitalist competition is!

    --
    "Old man yells at systemd"
  110. Re:GAYER THAN AIDS? by Anonymous Coward · · Score: 0

    Maybe his intent was to piss off idiots like you. He did a pretty good job at it. You seem to be pretty insecure yourself.

  111. Many eyes and colored hats by Anonymous Coward · · Score: 2, Insightful

    Ah, but how many of them eyes are wearing white hats, and how many are wearing black hats?

    In this case, the white hats working inside the Microsoft Compound had to turn a blind eye to these bugs in order to focus on their impossibly rushed deadlines. (Of course, now those same eyes are in panic mode since the leak.)

    Meanwhile, the white hats outside the compound walls are powerless to fix the bugs, through fear of legal repercussions: The very existence of any fix suggested proves that they saw the source without paying the license tax and signing away their firstborns to an NDA.

    The black hats, OTOH, shielded by anonymity and freed from the bonds of legal accountability and responsibility, they're free to see all the chaos, hate, and mayhem they can cause (and then go do it), secure in the knowledge that nobody can stop them.

    Sure, some of them will be slowed, as patches trickle out after the fact. Sure, some of them will be caught, as their own idiocy gives them away. But nobody can stop them, because more of the eyes looking at the sources, with the power to change them, are wearing black hats than white.

    This Windows disaster cannot afford to be called similar to the situation with Open Source Software. With the sources open, and the maintainers equally open, more of the eyes looking at the sources are wearing white hats than black. And thanks to the openness, the white hats are just as powerful, if not moreso, than the black hats.

    1. Re:Many eyes and colored hats by Anonymous Coward · · Score: 0

      And red hats. Don't forget the fedoras!

  112. Comspiracy by Anonymous Coward · · Score: 0

    Maybe the code was leaked on purpose. Think about it. They only leaked part of the OS, could anyone take that code and build a windows clone... probably damn few.. and even if someone were to use the code, they would be using stolen code. So, Microsoft may have just done two things: 1. They achieved the open source effect, that is, they now have some smart hackers looking at it that are contributing back... and secondly,all those ontributions they can put into the windows code base and everything is still proprietary. Maybe they should "acidentally" leak some more code.... like Internet Information Server.

  113. eh... its not really an IE problem... by MattyCobb · · Score: 5, Insightful

    i dont see why everone is going crazy over this exploit. i mean really... microsoft actually has already done something about this... its called get the NEW version of IE. Don't get me wrong, I am a big open source supporter, but seriously... oss would have made no difference here. Basically people just have to keep up to date with IE and patches to get around this. Same as if someone, however unlikely, found such a exploit in a mozilla product... or some other open source browser. the fact that it is open source and someone could find the bug faster means nothing if you dont keep your software up-to-date. And no, most casual Windows users don't. and no getting them to switch to a 'nix OS wouldn't change that.

    its really more of an education problem than a software problem. most computer users (not the /. crowd have no idea what they are doing....

    at least thats my 2 cents.

    --

    Matt
    You have 1 Moderator Point! Use it or lose it! Is that a threat? -vapid
    1. Re:eh... its not really an IE problem... by alleycat0 · · Score: 1

      Where i work, we are dependent upon Oracle 8.1, with which IE 6 has some incompatibilities, so we stick to IE 5.5. It took months to get Oracle set up properly - are we supposed to do this with every new release, *and* upgrade 2,000+ PCs every time every time IR or any other application is upgraded??

      --
      I am not a number - I am a free man!
    2. Re:eh... its not really an IE problem... by MattyCobb · · Score: 1

      Where i work, we are dependent upon Oracle 8.1, with which IE 6 has some incompatibilities, so we stick to IE 5.5. It took months to get Oracle set up properly - are we supposed to do this with every new release, *and* upgrade 2,000+ PCs every time every time IR or any other application is upgraded??

      if security is important to you than yes... thats pretty much expected. computers aren't static. if those computers have internet access i would hope you update their anti-virus regularly ect. thats the reason IT people get good money now isn't it :P

      --

      Matt
      You have 1 Moderator Point! Use it or lose it! Is that a threat? -vapid
  114. why BMP? by Anonymous Coward · · Score: 1, Funny

    bitmaps are not a particluarly clever choice to use on the Ineternet. there are JPEGs, PNGs etc. that are much better suited for the web. But as a side smirk - it is highly amusing to see microsoft products die trying to read microsoft formats

    1. Re:why BMP? by Krojack · · Score: 1

      arn't BMP files still the only format you can use for desktop wallpaper unless you enable that god awful active desktop which slows down the system 10 fold?

  115. Re: most effective SPAM subject line? by Frankensloot · · Score: 0

    Really? You believe all source code should be publicly available? Are you trolling, or are you really that obtuse? I'm just curious--does your ideology extend to other types of information, such as books, newspapers, recipes, the PIN number on your ATM card?

    Not to mention that it's completely stupid of you to argue that you're justified in looking at the source merely because you personally believe all source code should be public. Do you believe that all Doritos should be free (as in beer)? If you did hold such a belief, would you be justified in going to the chips aisle of your local supermarket, clearing the shelf of Doritos and walking out without paying?

    No, of course not. Because that's utterly indefensible. And let me tell you, I'd be standing there cheering on the supermarket security guards as they chased you down and tackled your lard-filled fat ass to the cold, dark asphalt.

    Jesus Christ, man. Grow a fucking brain.

  116. So, give up the broke-down Chevy & get a Porsc by Anonymous Coward · · Score: 0, Informative

    Besides giving you a more secure feeling, Opera's features will show you that IE is an uninspired lump.

  117. Palm does too by PetoskeyGuy · · Score: 2, Interesting

    Part of obtaining Palm Certification for your software involves surviving the Gremlins. You can't use the Palm logo on your program without it. It's even built into their emulator right on the menu. And yes you find some weird shit.

  118. what if it is not a bug? by spoonyfork · · Score: 1
    What if it is not a bug but intended to be there? Has anyone thought of that?

    /tinfoil hat

    --
    Speak truth to power.
  119. e viva la communisma e la liberta! by Anonymous Coward · · Score: 0

    give us more code, and we will strengten the whole windows system!

  120. 'Specially Crafted Image' by bokmann · · Score: 3, Funny

    That is a little funny... Isn't a 'specially crafted image' the same 'exploit' that Geordie LaForge came up with for introducing a virus into the borg collective? Remember the first episode with 'Hugh'?

    -db

  121. Conspiracy theory Re:so THATS why it was leaked by AlienRelics · · Score: 1

    I think MS had a hand in leaking it. Why? Because this is W2K and WinNT4 code. So now admins and their bosses will run in a panic to upgrade to WindowsXP.

    And the first hack published? Only works in IE 5. Gee. So the fix is to upgrade to IE 6. Another upgrade.

    I'm upgrading to Linux.

  122. Folklore.org link from Apple early days by tugrul · · Score: 2, Interesting
  123. And this answer... by Anonymous Coward · · Score: 0
    causes many people to switch to linux, mac, or to just pirate windows xp...

    It's a sad, sad world...

  124. Read MS source? yeah, Want brain damage? by Anonymous Coward · · Score: 0

    I agree!!!..who in their right mind would want to look at any source code produced by MS? Their products are not examples of well thought out concepts (eg:put OS code into dll's etc) and the constant erratic (on purpose?) behaviour of their products towards other products (netscape, Drdos, lotus 123), and who knows, mabey there are hidden "bombs" and timers at work...a friend of mine's win95 acts strange (buggy, slow) these days..(installed clean)...same with the wierd behaviour of win98se as time goes by...you couldn't pay me enough to even look at that code for one second...not to mention there is millions of pages of it. It's just an (movie/hackers/macho) fantasy that looking at MS code is going to get you anywhere in life...best look at real code (open source), written by smart people who don't play marketing/world domination head games.

  125. there isa goto in the quoted source by Yogurt+Earl · · Score: 0, Troll

    There is a goto in MS source code quoted for the exploit.
    DON'T use goto or you will be infringing on their copyright/IP.
    I hope no existing OSS use goto's because they're hosed. This probably means any project in Fortran is in big trouble!
    Hurry convert to java where goto's don't compile!!

    Yogurt Earl

  126. Microsoft leaked code to "FORCE" XP upgrades...... by Anonymous Coward · · Score: 0, Troll

    You wait and see. This is just the first pebble
    in a huge landslide that's about to come
    crashing down.

    Nobody was upgrading to XP (because it sucked and
    still continues to do so) so Microsoft arranged
    for source code to be leaked.

    The internet will become intolerable for all M$
    operating systems that are less than XP in version
    within 3 months.

    Microsoft is going to HUGELY recover from that
    "No-Gain" Quarter they posted.

  127. Nuclear missles incomming! Brace for impact! by argoff · · Score: 1

    As soon as I herd the Windows source was out there, I knew it was only a mater of time before the sunami reached the shores.

    Well the good news is that now at least the Samba folks will finally be able to figure out how they bastardized SMB.

  128. IE5.0 still accounts for the majority of browsers by Anonymous Coward · · Score: 1, Interesting

    My logs show that 75% of the traffic to my website are from IE 5. The remaining 25% are IE 6.0 and Mozilla Gecko based browsers.

  129. I realize I'm forfeiting my geek status by asking by jkauzlar · · Score: 1

    this, but how in the heck can you exploit a buffer overload to get full access to a system?! I've gone over it a million times in my head and can't think of a way to do anything but crash the program!

  130. use it for change! by tau_ · · Score: 5, Funny

    So, where's the .bmp I can link to my web site that makes IE5 remotely execute Mozilla Firefox installer?

    --
    Ask a silly person, get a silly answer.
  131. No, the FS/OS world does not insist on upgrades by JoeBuck · · Score: 4, Informative

    No, it doesn't work that way. All the major Linux and BSD distros backport security fixes into older apps that they have released; they do not insist that you upgrade to the next major version. When someone (e.g. Red Hat) drops security coverage for older versions, multiple efforts (Progeny, Fedora Legacy) spring up to fill the gap.

    1. Re:No, the FS/OS world does not insist on upgrades by Anonymous Coward · · Score: 0

      Fuck! Have you ever asked a newer version of old gcc in redhat 6.0? I personally know that redhat guys do not support older versions. You have to upgrade the whole os, not just the program itself.

      Slashdot guys don't even know how things are running on Linux!

    2. Re:No, the FS/OS world does not insist on upgrades by Anonymous Coward · · Score: 0

      Umm who says this bug hasn't been fixed. The code leaked was Win2k SP1 - how do you know if this bug still exists in SP2, SP3, SP4?

      Microsoft may have backported the patch to IE5 as well - the source code leaked is VERY old.

    3. Re:No, the FS/OS world does not insist on upgrades by Lost+Race · · Score: 1
      Exactly, and even if the distributor does not backport the patch, most one-liner buffer overflow fixes are trivial to backport manually.

      That's the best thing about using open source -- being able to fix small (but significant!) bugs without having to beg and plead and wait for someone else to do it, and without ever having to do a full upgrade (and the consequent reconfiguration and re-validation).

      I'll do a full upgrade on my own schedule, when I need new features and can afford the downtime, not whenever someone finds yet another buglet.

  132. Hmm.. by Anonymous Coward · · Score: 4, Funny

    I can see the ultimate virus now: you click an innocent-looking link, it takes you to a goatse bmp, and the exploit will lock your keyboard and mouse...leaving you utterly defenseless! Oh the horror!

  133. Win95 by phorm · · Score: 1

    IE6, which doesn't run on windows 95. This might not seem like a big deal, win95 is outdated... but when you've got a whole corporation with win95 and need new licenses in the thousands to replace it...

  134. The Exploit... by Anonymous Coward · · Score: 0

    M$.com

    ^is and was fixed prior to the release of the bug...I think?

    More info from the people that found the specifics

    \/
    eeye.com

    Correct me if I am wrong...isn't that the same bug that is being exploited?

  135. Who Runs IE 5 anyway? by vwjeff · · Score: 5, Funny

    I mean really, who runs IE 5 anyway. I'm sure that most corporate network admins keep up with updating IE. Let me check on a random company machine...

    Help-About Internet Explorer-.....Never mind my previous comment.

    1. Re:Who Runs IE 5 anyway? by BCW2 · · Score: 0, Troll

      The same thundering herd of dumbass that use any form of IE. Just like using hotmail or MSN, these are nothing but virus traps. Those that like catching the worm or virus of the week will continue to use them. The rest of us will use Mozilla, opera or even Netscape. Anything is better than IE.

      --
      Professional Politicians are not the solution, they ARE the problem.
    2. Re:Who Runs IE 5 anyway? by Anonymous Coward · · Score: 1, Interesting

      The company I used to work for still ran Windows 95 machines... IE 5 was prominent on all of their Win95 and Win98 machines.
      It would be unethical to disclose who that major manufacturing company is. Hehe.

  136. Open Source Coders by siphoncolder · · Score: 1, Insightful

    All that manpower, yet the most prominent face on this issue so far is an exploit.

    Is this how the OSS community at large operates? Instead of releasing patches, they release exploits?

    The issue as I see it now is: the OSS advocates with the big mouths tend to be the ones saying that ALL code should be open for public inspection, and that closed-source is bad for everyone. This new event however, seems to prove to the public at large that these "rogue" coders don't have the Public Good at heart at all.

    OSS coders should stick to OSS - let the closed-source companies and coders be. Mixing OSS coders with closed-source is kinda like mixing Communism with Money.

    --
    i'm amazed that i survived - an airbag saved my life.
    1. Re:Open Source Coders by Vegeta99 · · Score: 4, Insightful

      Doing ANYTHING with the code, good or bad is illegal. So if we DID make a patch, we couldn't claim we did.

    2. Re:Open Source Coders by pclminion · · Score: 3, Insightful
      Is this how the OSS community at large operates? Instead of releasing patches, they release exploits?

      There comes a point where releasing a patch would be ludicrous, because the problem and its solution are so obvious.

      It would be like calling up Boeing to report that the wing has fallen off your airplane, explaining why that is a problem, and giving them detailed instructions how to fix it. They know what's wrong and how to fix it. The problem is motivating them to do it.

      Time and again, MS has proven that the only motivation to fix problems is concrete exploits in the wild (and even then, they sometimes don't fix it).

    3. Re:Open Source Coders by vidarh · · Score: 1
      Professional developers would be STUPID if they spend any amount of time looking at Microsofts code, and especially if they comment on it in public. It would be a huge legal risk in case you ever find yourself employed by a company in direct competition with Microsoft.

    4. Re:Open Source Coders by miffo.swe · · Score: 1

      NO sane person in the OSS community is even poking at that pile of spaghetti with a stick! Doing that is a one way ticket to problems down the road. Be aware that script kiddies and virii writers and MS Windows security companies is the ones doing all the checking.

      Go away you troll!

      --
      HTTP/1.1 400
  137. Re:stop knocking Microsoft by BCW2 · · Score: 2, Funny

    That kind of thinking explains the collapse of the British Empire completly.

    --
    Professional Politicians are not the solution, they ARE the problem.
  138. Try Here by Ieshan · · Score: 4, Informative

    You could always check out the google Zeitgeist.

    http://www.google.com/press/zeitgeist.html

    Down in the middle of the page, it shows a graph that depicts MSIE 6.0 to be the dominant browser in nice clear red ink. :)

    1. Re:Try Here by Anonymous Coward · · Score: 0

      ...or it could be that everyone still running IE 5 still has their browser home page set to msn and has never heard of google. Now I don't know if that means there are more IE 5 installs than IE 6, but google is anything but a random distribution of internet users

    2. Re:Try Here by Anonymous Coward · · Score: 0

      That does not mean IE 6 has less bug/more bugs than IE 5... actually that means people "prefer" IE 6 to IE 5 which means "nothing". :)

      I prefer Mozilla Firefox to IE 6 and I will bet you a new hard-drive that most at MS think null of that also.

      l8r

  139. Simple: Write your congressman... by NotQuiteReal · · Score: 1
    ... to pass a law making all source code illegal.

    I am to busy at the moment, but the template to craft such a law, in reasonable terms has already been done. Follow the outline of the classic argument against water. Just search google for Dihydrogen Monoxide and you should get the gist - think how easy it would be to write a similar diatribe against software

    comp.risks ought to get you started.

    --
    This issue is a bit more complicated than you think.
  140. You have capitalism wrong by Anonymous Coward · · Score: 0

    Open source isn't 'communistic' -- it's capitalistic. Why? It increases competition.

    I don't know if one can label Open Source either 'communistic' or 'capitalistic', but you certainly misunderstand capitalism. Why? Because encouraging competition isn't what is fundamentally required to qualify as 'capitalism'. Look at the name. It's not 'competitiveness'. It's 'capitalism'. Capitalism fundamentally requires private ownership of the means of production. This is what allows investors to put capital into a business idea or product or piece of land or factory so that they can own part of it and later sell it, if they so desire, at a gain or loss. Yes, competition can come as a result of capitalism, and capitalism does nothing fundamentally to restrict it, but it is not required and it's certainly not how capitalism starts. It starts by allowing individuals (corporations came later) to create, own, buy, and sell. Capitalism is about ownership. Without private ownership, capitalism cannot work.

  141. Source Code Auditing Tools by cquark · · Score: 1

    There are a variety of static source code analyzers that will find potential buffer overflows and other types of security flaws. I like Flawfinder, but ITS4 is also good though it's licensing terms aren't as clear or free as I'd like. There's also Secure Software's RATS, which can analyze several languages in addition to C and C++. Each of these tools generates a large amount of output and you have to have some understanding of security to use them, but they can find potential security flaws that you would otherwise overlook.

  142. Lesson one, grasshopper... by nacturation · · Score: 1

    Somebody, please, monitor this bug (or teach me how to monitor it)

    1. Read Slashdot
    2. Wait for announcement of fix
    3. Attain Enlightenment

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  143. Re:stop knocking Microsoft by Krojack · · Score: 1

    quality? where? I must have missed something.

    I was a hard core windows person doing my best to backup MS until I was forced to learn linux at my job. I saw how it was 20 times easier to manage a linux box over a windows box. I started using Linux with X full time. I will NEVER go back to using windows full time.

    I guess you can say I was freed from Microsoft's version of "The Matrix" :)

  144. What's your point? by schmaltz · · Score: 2, Interesting
    You don't agree and the idea's old... so what? The idea ain't goin' away... just because it's impossible to prove doesn't mean it's not worth mentioning. Also impossible to determine was who had the greater motivation-

    Microsoft, with a couple hundred million users they'd really wouldn't mind being compelled to buy their next O/S

    Or some surly hacker who doesn't care if he loses his job?

    Fear is a powerful motivator against the latter... and Microsoft's greed, which has compelled them to illegal market-manipulating tactics in the past, seems the greater force. We haven't seen much response from Microsoft about the source leak, yet it may prove to be the 9/11 for the computer business, if virus writers get busy with it.

    --
    Big Daddy, Johnny, Burp, Aunt Zelda, Scott, Slurp, Big Momma ... where's Siggy?
    1. Re:What's your point? by thebatlab · · Score: 1

      "You don't agree and the idea's old... so what?"

      So that means I'm able to post my disagreement about continually posting the idea for what is now in my mind, and the minds of a lot more people, a quick karma boost. How can a continually repeated post get modded as "insightful" when it's been repeated ad naeseum? The idea of an insight is very few people have thought of this before. There is a "redundant" mod type though. Maybe people should use that in the right circumstances more often.

      "We haven't seen much response from Microsoft about the source leak"

      Do you want them to start a blog? Of course they're not saying much b/c it's an internal matter that is currently under investigation. You know when police say "The investigation is underway at this time and I can't comment on it"? Same situation. They aren't going to jump the gun with anything though they have posted how it's not related to the Shared Source initiative which may dissuage arguments that it was done to discredit the open source model.

    2. Re:What's your point? by schmaltz · · Score: 1

      I don't need karma, so that's not it...

      However, it's a very important topic, because whether or not the conspiracy innuendo's true (short of an indictment we'll never know), it's the outcome of the release that will be the future worry ... endless virus campaigns, forcing Microsoft to drop support for current products, requiring licensees to upgrade to TCP-compliant hardware and operating systems, government pronouncements on the subject (or worse, mandates), ISPs shutting down the relatively unfettered protocol usage we enjoy today.

      With that much source code on the loose, these outcomes are likely become the topic of many future /. articles... so get used to it!

      --
      Big Daddy, Johnny, Burp, Aunt Zelda, Scott, Slurp, Big Momma ... where's Siggy?
  145. Back doors... by Anonymous Coward · · Score: 1, Interesting

    It has been mentioned that the leaked source code might reveal some long-suspected back doors... I wonder if these and other unknown vulnerabilities were secretly known to MS and others, and are in fact the back doors?

  146. Isn't favicon.ico an icon, and thus a bitmap? by Anonymous Coward · · Score: 0

    Would it be possible to exploit IE5 simply by being added to Favorites?

  147. Does this mean that if I write a virus circa 1994 by Assmasher · · Score: 1

    I can claim that I can infect your PC w/o mentioning that you need to be running an obsolete OS...?

    --
    Loading...
  148. Re:Well sucks but - NO! Wrong Job by freeze128 · · Score: 1
    When microsoft declared security as their main goal ie5 was the current browser. ie6 has it fixed so they obviously wen't trough their stuff to fix it.
    Doesn't MSIE 6.0 use the Gecko engine to render web pages? Isn't that what mozilla used? Isn't mozilla open source? How is that "Doing their job"?
  149. Oulook using IE engine to render HTML email by FutureShoks · · Score: 4, Interesting
    Does Outlook use this portion of the IE engine to render HTML emails?

    Therefore, if I was to run IE5 and Outlook and was to render a piece of spam with a malicious image, could I be open to attack?
    --
    ___FutureShoks___
  150. #!/usr/bin/shell by bani · · Score: 1

    no it wont, because it's not +x

  151. No longer a thought experiment by bshroyer · · Score: 2, Insightful

    Point well taken. My response may have been a bit flippant.

    As a thought experiment, imagine the following contest:

    a) 1000 Linux developers are given (full) WinXP source code and locked in a room to find potential exploits.

    b) In another room, 1000 WinXP developers are locked in a room with (insert distro here) source code to find potential exploits.

    Which group finds more holes in a week? Which group finds more serious holes? Up until last week, this was purely a thought experiment, with OSS claiming the virtual victory. Last week, it became real.

    (And don't you think that it's possible that Microsoft has been conducting contest (b) FOR YEARS trying to find holes to prove OSS insecurity?)

    --
    The cure for cancer is coming: Reovirus
    1. Re:No longer a thought experiment by MoneyT · · Score: 1

      Actualy, I highly doubt MS has been. Because those 1000 developers are being wasted. They could be bringing windows futher ahead of the competition (note I'm speaking from MS viewpoint, not from a standard view) but instead you have them trying to poke holes in the current version of the competition.

      There's an old saying about advertisements that the leader in any field will never mention it's competition in advertising. So would it be with MS, they have the lead for now, so most of their efforts are going to go to keeping that lead, not bringing the other guy down.

      --
      T Money
      World Domination with a plastic spoon since 1984
    2. Re:No longer a thought experiment by sholden · · Score: 1

      Clearly the WinXP developers would win since having produced so many security flaws they know exactly what to look for... boom - tish.

      And no Microsoft probably hasn't been doing such a thing for years. There's no need enough security holes are found in OSS by OSS developers themselves to give MS all te FUD they need.

      If Microsoft cared they could just look at fetchmail, it would single handedly destroy everything put forward in that cathedral and the bazaar thingamejig.

    3. Re:No longer a thought experiment by bshroyer · · Score: 1

      An excellent, often overlooked point you make: OSS != high quality.

      There is a TON of crap out there in OSS space.

      --
      The cure for cancer is coming: Reovirus
  152. Free as in beer helps as well by tepples · · Score: 3, Insightful

    where would you get free patches for Red Hat 7.3?

    I think the point is that you can patch Red Hat 5.x for free by upgrading to a more recent version of Red^H^H^HFedora for no charge. IE 5 is the last version IE to run on Microsoft Windows 95, and Microsoft charges for newer versions of Windows.

    1. Re:Free as in beer helps as well by GlassHeart · · Score: 3, Informative
      I think the point is that you can patch Red Hat 5.x for free by upgrading to a more recent version of Red^H^H^HFedora for no charge.

      Please read the original post I was responding to, which states:

      Unless your arguing that staying current is the only way to avoid exploits, then your making a strong argument that the TCO of Open Source should be sung from the moutain top.

      I'm not going to respond to each response with the same message, so here it is:

      The IE situation is the worst. You probably have no choice but to upgrade. In this case you can probably download IE 6 for free, but for other exploits you may have to pay for a newer version of Windows. Hear me, it's the worst.

      The open source situation is better. You at least have the source, and at the worst case can go patch it yourself or pay somebody to patch it. Some investment in time or money can enable you to stay with an older version to avoid upgrading.

      However, open source doesn't solve all the problems. If there's no volunteer to keep an old version patched, then there's some cost on your part if you don't want to upgrade. Upgrading, on the other hand, contains some risks (which may translate to cost as well). For one, the new features may contain new exploits.

      Which is why I wrote that insisting on running Red Hat 5.0 may be expensive, even though it's open source. It's entirely possible (which is good, and better than IE or Windows), because you have source, but it may not be viable, despite having the source.

      Somebody brought up Debian. Yes, Debian maintains an excellent stable distribution. However, not even Debian volunteers patch every old version. At some point, "testing" becomes "stable" and the old "stable" will be left to rot. If you insist on running the old one, then your personal TCO will increase significantly.

      And now the obvious conclusion: not even open source can make not upgrading a viable option forever. At some point (obviously at different points for Windows compared to Red Hat Linux) it's cheaper to upgrade. That's all I'm saying.

    2. Re:Free as in beer helps as well by dolson · · Score: 1

      Not sure if you know already or not, but Debian is pretty easy to upgrade from one version to the next... Two commands, really: apt-get update ; apt-get dist-upgrade. Still cheaper than upgrading Windows.

    3. Re:Free as in beer helps as well by Anonymous Coward · · Score: 0

      Nice, goatse. Try this Fedora link.

    4. Re:Free as in beer helps as well by tepples · · Score: 1

      You'll find that a lot of sites will block anybody coming from Slashdot. Bugzilla does it. Even fedora.redhat.com has Referer protection.

    5. Re:Free as in beer helps as well by GlassHeart · · Score: 1
      Not sure if you know already or not, but Debian is pretty easy to upgrade from one version to the next...

      The cost I was talking about is a potential cost for instability introduced by the new features (that you didn't really need) when you upgrade. A new version almost certainly brings new bugs, and also configuration mistakes and other user errors into your system. On a production server, you do not upgrade lightly.

      Ideally, you pick a version with the features you need, and get continuous security, optimization, and bug patches until it is as close to perfect as humanly possible. You would upgrade only when you need a new feature. What I was trying to point out is that from a TCO perspective, staying with really really old software is still not viable, despite it being open source.

  153. Re: most effective SPAM subject line? by flossie · · Score: 2, Insightful

    I'm just curious--does your ideology extend to other types of information, such as books, newspapers, recipes, the PIN number on your ATM card?

    I don't know about the original poster's ideology, but I certainly expect to get the "source code" to a book when I buy one, or even when I browse in the bookshop or library. I expect to get the "source code" to a newspaper when I buy one, or when I flick through it in the newsagents deciding whether it looks interesting enough to buy. I generally expect to be able to read recipes when people give them to me, and I *definitely* expect pre-processed foods to contain a list of ingredients when I buy them.

    As for PIN numbers, I have never tried to sell my PIN to anyone, so I don't see what right anyone has to know what it is - but then you were just being flippant with that comment, weren't you?

  154. lossy subject lines by Anonymous Coward · · Score: 0

    Slashdot limits subject lengths. Please don't count off for lossy compression of text required to fit it into 50 or so characters.

    1. Re:lossy subject lines by Anonymous Coward · · Score: 0

      Two things, my friend:

      Your subject has... well, count 'em, less than 50 or so characters.

      I wasn't really being that bitchy about your subject, but I had just finished reading a great SF story in which the author (editor shares blame, too) kept booting back into my own miserable world by making the same grammatical mistake you did. (could of, would of, should of)

      It made me nuts.

      Of a nice day! :)

    2. Re:lossy subject lines by Anonymous Coward · · Score: 0

      What gets me is that you used it ("may not have..") properly in the body of your post. Gads.

    3. Re:lossy subject lines by Anonymous Coward · · Score: 0
      Fucker posted anonymously too, so we can't put him in our killfiles.

      Have course I'm kidding!

  155. No original thought anymore. Fear! by tomstdenis · · Score: 1

    What exploited? I didn't post code. In fact the code I have posted [not here of course] properly uses unsigned types.

    And in fact I never said "an int C-type". I said "int" as in short for "integer". And how do you know I didn't mean unsigned int?

    Anyways, the fact I have an archive going back over a year of crypto code that uses unsigned over signed ints shows I know this "fact" already.

    Tom

    --
    Someday, I'll have a real sig.
  156. Lots of people still run IE5.5 by smallmj · · Score: 2, Informative

    I see lots of posts here from people saying "Just upgrade to IE6.1. The problem is that there are lots of people out there that can't or won't.

    (1) There folks still running Win95 that are stuck. They've got an old Pentium 166, and have no legitimate way to upgrade to Win98. Have you see upgrade copies available in the last couple of years? Sure they can find a copy on ebay, but lots of these folks would never think of that.

    (2) There are folks with Dial-up who didn't want to tie up their phone lines downloading the beast. These folks should definately do it now, but they haven't had a really compelling reason.

    (3) They may not know how. "Windows Update, what's that?"

    I do lots of work for clueless users, and trust me, their are PLENTY of IE5 boxes out there.

    Mark

    --
    ------- Mark
  157. It is exploitable by JustKidding · · Score: 1
    I thought i had it figured it out: it's not exploitable.

    The only way to get past the cbSkip > 1024 check, is to make sure it's negative. But in that case, Read will attempt to read at least 2^31 bytes (because the parameter is an unsigned integer), and either return 0, because it reached the end of the file before being able to read that many bytes (d'oh), or cause an access violation because it overran the buffer so far that it actually overran the stack and tried to write outside the process' memory.

    But when Read returns 0 before overrunning the stack completely (shouldn't be hard, just don't make the file too big), it can try to clean up, but it'll have to return sometime, and the stack is already corrupted. So in the end, i do think it's exploitable.

  158. Windows patches scrutinized by igny · · Score: 1

    Next thing we will know, the enthusiasts will go through all Windows patches released up to date, and compare them with the leaked code. Moreover, EVERY new patch will be scrutinized to check whether the leaked code had the flaw, which was fixed by the new patch. Then there will be debates on whether the leak helped fo find the flaw...

    --
    In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
  159. So lemme get this straight by melted · · Score: 1, Flamebait

    They've found a bug in a version of IE that's TWO FUCKING YEARS OLD. Subsequent versions are not affected. Is this all this "many eyes" approach capable of?

    1. Re:So lemme get this straight by Budgreen · · Score: 1

      no, this is the M$ version of many eyes, results may vary.

      --
      The greatest right given is the right to be wrong...
  160. Use CQual by Anonymous Coward · · Score: 1, Informative

    http://www.cs.berkeley.edu/%7Eushankar/research/pe rcents/index.html

  161. My apologies by HiThere · · Score: 1

    I said that I didn't think this code release could hurt MS...And I've already been proven wrong. So ...
    I appologize.

    (I'm not about to think nice things about MS, though.)

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  162. that's very false. by zoloto · · Score: 1

    You are allowed to use copyrighted information to some extent for certain purposes such as educationl, parady, etc. You can use a small clip from a song, you can display a paragrahp from a book, etc. I doubt anyone would consider showing 10 lines or so of source code out of millions a copyright violation. The grandparent post is obviously for education purposes only : )

    I'm not sure where you're getting that information but I can tell you, you're wrong. Using other people's writings, music or even code ()if you want to bring it that way can be looked at as infringements. Even parodies. Ever notice how on songs they change the notes, pitch or key of a song so that it doesn't mirror exactly and prevents it from being recognised as the origional (besides the lyrics obviously)? Professional journalists (and their companies) can't rebroadcast any news without permission by the owner ie. the AP or another news wire. This includes stories, articles and television and radio news broadcasts. The same goes for music. It's been said that even copying two notes is infringement.

    Not that I'm in agreement with the two notes bit, this is an actual poster with factual information that counters the top 10 myths of copyrightts in news.

    I'll post back when I can find a link or give the exact name.

    So that said, even posting 10-15 lines of someone elses code without proper permission (assuming you had legal access to the source) is still wrong.

    Not that I like playing devil's advocate or anything, but even in acedemia these rules can apply and typically do. itt prevents plagerism and dishonesty.

    1. Re:that's very false. by AstroDrabb · · Score: 1

      Are you sure? I though I read somewhere that you could use a small part of a copyrighted work without permission. Obviously re-broadcasting an entire news story would need permission. Read this post. I am not sure if it is correct, though it does sound familiar.

      --
      If Tyranny and Oppression come to this land,
      it will be in the guise of fighting a foreign enemy. -James Madison
  163. nt4 source by Anonymous Coward · · Score: 2, Informative

    I don't know why everyone is raving so much about the windows 2000 code. The NT4 code that leaked is much more interesting, containing a lot of the networking and security code that the 2000 leak misses out.

    A couple of links are here:

    ed2k://|file|windows_nt_4_source_code .zip|241131483|7a8b8624a5014a3f2c586c813568be09|
    ed2k://|file|windows_nt_4_source_code .zip|241131483|afcb4b1fd05ed574e2ee77618222621d|


    I have downloaded the first one. It contained a minor bit of corruption in the zip file. The second one may be more pure, but I don't know as I'm only 90% complete with that.

    Though I have to say, the bugcodes.txt file in the windows 2000 archive was a fascinating read.

    Also, I hear rumours that there is a longhorn source code leak out there. I noticed it was available on overnet, but with no sources available to me, I couldn't download any of it to check. Can anyone confirm?

    ed2k://|file|windows longhorn build 4008 source code (partial) .rar|1357906140|dba2a19a3c822837ad6ade3b7f178862|

    1. Re:nt4 source by Anonymous Coward · · Score: 0

      I totally concur. You should check out private\ntos\cntfs in the NT4 sources, especially the spec folder. It's the full NTFS source code and specification documents! VERY interesting indeed.

    2. Re:nt4 source by Anonymous Coward · · Score: 0

      Please report back on the second file. Saves the hassle of a 200 meg download if it's corrupt too.

    3. Re:nt4 source by Anonymous Coward · · Score: 0

      Check this thread in a couple of hours, I'll have some information for you then. It's currently stuck on 99.85, rather frustratingly!

    4. Re:nt4 source by Anonymous Coward · · Score: 0

      Ok, both of them are corrupt. I'll try to fix them later though, maybe the two of them can be used to generate a complete pure one.

    5. Re:nt4 source by Anonymous Coward · · Score: 0

      I found that InfoZIP's unzip utility can extract the files from them with no errors. However, pkzip, winzip and winrar have problems. Most bizarre!

      The file they fail on is the one just after nt4/private/ntos/ntl/alpha/largeint.s

  164. Code Audits by the+eric+conspiracy · · Score: 3, Interesting

    So the old theory that keeping source code secret will help prevent security attacks has now proven to be invalid, for the reason that you can't be sure that the code will in fact reliably remain secret. When the code inevitably gets out you will have a shitstorm of problems.

    Now open source has in reality been proven the best way.

    And security by obscurity fails again.

  165. Re:stop knocking Microsoft by Anonymous Coward · · Score: 0

    Don't you mean boxen?

  166. Only... by SuperKendall · · Score: 1

    By any chance, did the program come up with the entire works of Shakespear?

    Only when run in a very large cluster.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  167. That's odd, I was just thinking of doing this... by chrootstrap · · Score: 1

    That's so wierd. Just last week I was thinking of crafting this very kind of exploit or one using a jpeg. Its interesting to consider how much blind acceptance of formatted data goes on... Perhaps a Word document could do such a thing as well, eh. A PDF? An Mpeg? lol... don't worry, it's not like people run as administrator all the time. ;)

    --
    Hacking articles at http://www.geocities.com/chroo
  168. MOD PARENT UP PLS by LordKazan · · Score: 1

    Very insightful post.. and i just ran out of mod points a few minutes ago

    --
    If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
  169. Leak source - brilliant strategy for Microsoft by Anonymous Coward · · Score: 0

    Now that Nt4.0 and 2000 OS source is out for everyone to see and download, I bet Microsoft sales folks are pushing Window XP for the corporate world. Just imagine all the new license agreement for Window XP next 6 months.

    Brilliant strategy from Microsoft Marketing.

  170. Re:I realize I'm forfeiting my geek status by aski by Xonea · · Score: 2, Informative

    I recommend reading Smashing the stack for fun and profit.

    It's very informative.

  171. A BITMAP file can cause trouble?? by frdmfghtr · · Score: 1

    Keep in mind that this comment is being posted by a non-programmer.

    It's a sad state of affairs when a BITMAP picture can be used as a security exploit. What next, loading a specially crafted text file into notepad? (err, I better be careful, that my have been doen already...)

    --
    Government's idea of a balanced budget: take money from the right pocket to balance...oh who am I kidding?
    1. Re:A BITMAP file can cause trouble?? by Anonymous Coward · · Score: 1, Insightful

      It's funny you should say that, because I was wondering the same thing. However, I am a programmer, and quite a good one too, so I checked the notepad source (in /win2k/private/windows/shell/accesory/notepad) and I can assure you that there is no way whatsoever that this could occur.

    2. Re:A BITMAP file can cause trouble?? by bruns · · Score: 1

      Been there, done that. If I remember from a few years ago, you could load a file into wordpad that would make it barf.

      --
      Brielle
  172. I read this book... by lostguy · · Score: 1

    it was called "Snow Crash"!

  173. Re: Not running as Admin or Root != safe by Lord+Bitman · · Score: 4, Insightful

    This is an exploit which effects Users, running a WEB BROWSER. Please tell me one single (however insignificant) thing a Normal User who is running a web BROWSER could possibly give half a fuck about which requires administrator privledges.

    Seperate user accounts, securing the system itself, etc, that is _ONLY_ security-related when you are the administrator of a server and require your box be up 24/7 (or at least somewhat often)

    Think about it for two seconds: You're a normal user, you're using your personal computer. Hell, you're using it to surf the web, this isnt any system which other people are dependent on having a high uptime or anything. You go to a webpage, and some arbitrary code gets executed.
    What files could be effected? Well, you're running as a normal user, so luckily for you only the files which you give a shit about will be harmed, while the easily replaceable part of the system remains intact.

    This whole "multiple accounts == security" line is pure bullshit extract. The files which a USER, not a System Administrator, cares about, are files which that USER created, downloaded, edited, etc. Files which the User has access to.
    If some malicious code executes as root/Admin, so what? Your important files are trashed and you need to spend an extra hour reconfiguring your system? That extra hour or two doesnt mean squat compared to the years it may take to restore the files which you created personally.

    "You Should Keep Backups anyway" is Irrelevant. As that can just as easily be applied to root-accessible files, the point is that non-admin privs are just as bad as admin privs on a personal system.
    And this exploit _is_ talking about a personal system, unless you're in the habit of running IE5 on a high-priority server instead of the laptop sitting next to it.

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  174. Re:I realize I'm forfeiting my geek status by aski by NoOneInParticular · · Score: 2, Informative

    Try this for a start.

  175. Everyone allready knows windows source! by Anonymous Coward · · Score: 0

    10 x=1 20 x=x+1 25 if x mod 2 = 0 then 30, else 40 30 Print "Explorer has experienced a problem and must be shut down" 35 goto 10 40 Print "What can the butterfly do TO you?" 45 goto 10

  176. Blackhats is what worries me. by miffo.swe · · Score: 2, Insightful

    Blackhats like CIA, KGB, China intelligence etc have had access to this code for much longer no doubt. Anybody think that MS delivering of the code to china hasnt been propagated to their intelligence agency? This only shows that there are no security in hiding security mechanisms. A quick glance at the crypto industry should be pretty revalating to MS.

    MS i in for a ride and it should be hammered around that most of theese exploits would NOT be stopped by Palladium. Palladium is just a buzzword and does not stop errors in protocols or implementations of them. Thats not going to stop MS from marketing palladium as a tool to stop errors in their code.

    --
    HTTP/1.1 400
  177. Your traffic is atypical (or you're making it up) by lseltzer · · Score: 1

    Google's traffic is overwhelmingly IE6. See the graph http://www.google.com/press/zeitgeist/jan04_browse rs.gif ("Web Browsers Used To Access Google, March 2001 - January 2004") on the page http://www.google.com/press/zeitgeist.html

  178. Only on Slashdot... by bonch · · Score: 1

    Only on Slashdot is it an issue that you have to download a newer version of something to fix a flaw. "Where can I download the patch for IE5?" It's called IE6.

    1. Re:Only on Slashdot... by Ulven · · Score: 1

      And how is Linux meant to stop the person using the computer from walking away with a CD full of Windows?

      Not to mention that it was here on /. that I read how it had been leaked, which, of course, meant that it mentioned the fact that it was from a Linux machine.

      Oh, one last point. I'm on a modem. How long will it take me to download IE6?

      (ok, so I'm not on a modem, and use firebird/fox. The point stands.)

    2. Re:Only on Slashdot... by SirTalon42 · · Score: 1

      Actually, the date that it was on a Linux machine (apparent from when the vi core dump was created) was before when it got the virus that created all the .eml files... just get the file listing, and look at the dates

      Of course that doesn't mean it couldn't of been on a Linux machine at a latter date (also doesn't mean it couldn't of been on a Windows machine) when it was leaked.

  179. Sorry about the busted links by lseltzer · · Score: 2, Informative
  180. Re: of been by Russ+Nelson · · Score: 0

    "Birds have a feather"? Wait, let me go look .... no, our birds have many feathers.
    -russ

    --
    Don't piss off The Angry Economist
  181. Thanks for that great writeup by Anonymous Coward · · Score: 0

    nice public service

    1. Re:Thanks for that great writeup by Anonymous Coward · · Score: 0
      nice public service


      Not sure if you meant this sarcastically. But, really, it is a good public service.

      Reading good code is just as important as reading bad code (as long as said code contains an explanation of why it is Good/Bad). A budding programmer needs to know the common mistakes in order to avoid them.

      "Those who do not study history are doomed to repeat it."

  182. Re:GAYER THAN AIDS? by Anonymous Coward · · Score: 0

    #include

    Please RTFA before flaming the poster.

  183. A simple binary patch by Russ+Nelson · · Score: 1

    A simple binary patch will fix it. Just change the jump instruction from a jge to jae (or jl to jb, as needed).
    -russ

    --
    Don't piss off The Angry Economist
  184. Legitimate reason to view the code by wombatmobile · · Score: 1

    You are allowed to use copyrighted information to some extent for certain purposes such as...

    preparing for and responding to security exploits that are based on the (now public domain amongst villains) leaked Microsoft code.

  185. Representative by rixstep · · Score: 2, Interesting

    This shouldn't be a discussion about whether open source is inherently more stable (which it surely is). What the leak gives everyone is a chance to see into the coding practices of Redmond. That is what is interesting.

    No one thought they were stellar; some already knew how bad things are; some figured, naturally, that if you could poke holes in their stuff like we've seen, something must be very, very wrong.

    But now people are going to see with their own eyes - and that, I insist, is what is interesting here. So keep your eyes peeled (sorry, PJ).

  186. Behold Citizens! Let the games begin! by Anonymous Coward · · Score: 1, Informative

    Unlike Linux which was born in the open and relies on inherently good code for security, MS went with the fallicy: security through obscurity. When I studied cryptography in university, I remember being told by many profs: "if your security relies heavily on people not figuring out the method, you get an F". Before RSA commercialized, the Americans and Russians used it for security --using the product of two large prime numbers as an exponent in a function that can encrypt/decrypt a message. The Americans know the Russians use it, and the Russians know the Americans use it. The method isn't a secret, the security lies in the difficulty of factoring large prime numbers. And (as one of my crypto texts explained) "If someone tried to create a database of all primes 512 bits or less in length, you couldn't do it, for if you could create a hard drive that could store 1 gigabyte of data on 1 gram, the list of primes (there are 10^151 of them) would require a hard drive whose weight would exceed the Chandrasekhar limit and collapse into a black hole (and unless you come up with a unique way of getting the data past the event horizon), you are hooped. Relying on the 5 year old 'I've got a secret' method of security works really well if you're 5 years old. A survey of 5 year olds agree "Security through obscurity works". 6 year olds weren't so sure. 10 year olds refuted the study. Microsoft was unavailable for comment.

  187. The file is crafted to exactly the right number... by Ayanami+Rei · · Score: 1

    ...of bytes so that it will overwrite the stack frame as needed, but not cause an access violation. Furthermore, a read past the end of a file does not cause the Read to terminate, but to read until EOF and then return the number of bytes it didn't get... (usually you store that result, and then do a select/poll loop to look for more data written to the end later on, until you get 0 back, which means you're done).

    So yeah, it actually does exactly what you want. A Read with an unchecked buffer and a very large size parameter is a h4xx0r's wet dream.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  188. NOW I GET IT! by Gezzwho · · Score: 1

    Thats why i takes sooooo long for micorosft to make a new OS. A couple of months to actually make the code, and a couple of years to make some gov. holes into it :)

    --
    Never argue with an idiot. He/Shell just drag you down to his/her level, and beat you with experience.
  189. ps - you don't need LFS to get UID 0 != root by Ayanami+Rei · · Score: 1

    Just change it in /etc/passwd and /etc/shadow
    Also, look for instances of it in /etc/security and /etc/pam.d

    (some scripts/PAM config stuff in those directories like to refer to "root" the username for stuff)

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  190. Re: Not running as Admin or Root != safe by chrootstrap · · Score: 1

    The basic difference is that the admin or root account is generally used to install, modify, and delete/uninstall executable programs. While this doesn't always work perfectly (e.g. PATH=~/bin, executables (including plug-ins) owned by the user, etc), this goes a long way to protecting not only users but yourself as well. So, if the admin account hasn't been compromised, you should feel fairly secure that when you run IE it doesn't have a virus infection, backdoor, etc.

    I agree that user-created documents are generally more important to the user than some .ini file used by an input method, etc. However, that has very little to do with security. If the user wishes to secure those documents, then backing them up, etc, makes some sense, no? However, consider that very few worms/viruses actually trash systems these days. They'd rather be stealthy; stay hidden and exploit the user's computer. Restricting admin access will improve the security in that scenario.

    Personally, I like how seemless Mac OS X has made it such that, when you do need admin access, it simply prompts you for the password in a dialog. It's easy and secure.

    --
    Hacking articles at http://www.geocities.com/chroo
  191. Was this leak accidental? by Anonymous Coward · · Score: 1, Informative

    Perhaps if some of Microsoft's code finds its way into Linux (accidently), then Microsoft can sue the living daylights out of opensource? They have the financial resources to do so. Imagine, the next killer app for linux: Windows NT (code). It just may legally "kill" Linux in the same was SCO would like to. What can be done to ensure that this code is kept out of opensource projects? That would be a mess.

    1. Re:Was this leak accidental? by CaptainTux · · Score: 3, Interesting
      What can be done to ensure that this code is kept out of opensource projects?

      The nature of open source software makes actually verifying the existence or non-existnece of code very easy. Microsoft wouldn't even need to contact anyone to tell them they thought they were including Microsoft code in their product. They could just download it and check. As could everyone else.

      The main problem is, and this is why I think MS has not actually gone to court against major oss projects yet, is that doing so would force them to show the offending lines of code in order for it to be compared to the oss source. If this incident has shown anything it is that revealing source is not something Microsoft wants to ever do -- even for products that are near or at/past EOL.

      That said, I think that project managers REALLY are going to need to be vigillent in monitoring contributions to their projects especially when programmers claim to be introducing Microsoft compatibility with the code. Chances will be good that some unethical programmers will try to slip some Microsof owned code into a project. I can actually see some pro MS people joining oss projects just to try to do this then notify MS so they can take legal action. But, if a project manager is doing their job, this should be an easy problem to fix.

      --
      Anthony Papillion
      Advanced Data Concepts, Inc.
      "Quality Custom Software and IT Services"
    2. Re:Was this leak accidental? by cjpembo · · Score: 1

      For instance and purely hypothetical; the WINE project may include a new feature or compatability that microsoft may claim could only have been "figured out" by reading their code, not reverse engineered. In addition, some of MS's code probably came from the BSD's, so it is possible that their are similar peices of code in free and MS code allready. It would be a shame if opensource projects have to provide a burden of proof if accused by MS of copyright infringment.

      In addition, how does a company like MS let this happen (code leak)?

      Personally, I wish MS would do what Apple did; use a superior UNIX OS as a base and write a compatability layer on top to run native apps. Who wouldn't jump at the chance of using linux and windows technology on the same machine simultaneoulsy. Linux for the kernel and security and everything else it does, and all the MS apps on top. They would get my 100 bucks if it worked, in a heartbeat.

  192. Is this what you seek? by the+web · · Score: 1

    User agent stats are approximately the following.

    93-96% IE
    Appx 3-4% Netscape.
    Appx 1-2% Alternative browsers.
    Of IE user agents, 78-80% is IE6 and the rest (mostly) is ie 5.x

    Thus, one in every five views is probably IE:5.x

    These are the recent stats of sites that I have had privvy to work on. These sites have a large audience as well so we (I) can assume it is an accurate poll.

    --
    __
    Thou hast besquirted me, O leotarded one.
    1. Re:Is this what you seek? by Ciggy · · Score: 1

      Are these stats of actual browsers, or what the browsers report themselves to be?

      I'd suspect that they're what the browsers are reporting themselves to be; this is akin to problems that have occurred with the census people when people have to state something, eg: in the United States, a 10-yearly census found more people in the 65-70 age band than in the 55-60 age band 10 years earlier and the difference could not be accounted for by immigration.

      Until [all] sites are no longer browser demanding, these [self-given] stats have to be taken with a pinch of salt.

      --

      A rose by any other name would smell as sweet;
      A chrysanthemum by any other name would be easier to spell
    2. Re:Is this what you seek? by the+web · · Score: 1

      Are these stats of actual browsers, or what the browsers report themselves to be?

      Well since I'm not staring over the shoulders of each member of the audience, it would have to be the latter. Salt is required with all reports like this though. Statistics can be used to prove anything afterall, 87% of people know that.

      --
      __
      Thou hast besquirted me, O leotarded one.
  193. Re:No original thought anymore. Fear! by Anonymous Coward · · Score: 0

    Wow. I haven't seen this much spin control since Al Gore invented rap.

  194. Take That Back! by Anonymous Coward · · Score: 1, Funny

    We, the members of MSDA (Monkey Software Developers of America), are deeply offended by what you imply. We are much better developers than MS and smell better too.

  195. vulnerability = exploit by kaisa_sosey · · Score: 3, Insightful
    In this case it doesn't take a genius to get a exploit from the vulnerability. Now tell me how one should possibly explain the vulnerability without giving a strong hint on how to build the exploit ? How about:

    Please change your browser because otherwise you will get rooted (i cannot explain why, please, please believe me).

    Would you take this serious ? And what amount of time would it take to find a exploit for a explanation like this:

    Found a serious buffer owerflow in IE when loading a bitmap image...

    This would result in exploits in a couple of hours and would give only the false impression that there are no exploits up to now...

    The source code is leaked since friday and you don't gain anything by telling only Microsoft that this and that vulnerability exists. Till they fix it its to late. And without a proof of concept everyone could claim he found a serious bug.

  196. This reminds me of "The Borg" by Ziviyr · · Score: 1

    Did you hear about the image that kills your collective whenever you view it?

    --

    Someone set us up the bomb, so shine we are!
  197. Bug Heritage by psychofox · · Score: 1

    I wonder if its been confirmed that the bug is in Microsoft produced code. I seem to recall that a (large?) portion of IE was originally NCSA Mosaic code. Wouldn't it be amusing if, after all the self-righteousness, it turned out to be (to some extent) not their fault...

    1. Re:Bug Heritage by Anonymous Coward · · Score: 0

      That was only versions of IE prior to 4.0, which was a complete rewrite from scratch. So, no it would not be Mosaic code at all!

  198. Bmp based exploit? New Slashdot logo anyone? by Anonymous Coward · · Score: 0

    ...now whenever an IE5 user visits Slashdot, a proggie will be installed which will nag the user to install Linux every 20 minutes, until they procalim their hard drive in the name of tux!

  199. Re:Microsoft leaked code to "FORCE" XP upgrades... by Anonymous Coward · · Score: 0
    Nobody was upgrading to XP (because it sucked and still continues to do so)

    Spoken like a true non-user of XP. Windows XP is, in fact, the best desktop operating system availble for the PC today.

  200. I know this is not a popular opinion but... by readpunk · · Score: 1

    I am glad to see this happen and I hope that this allows not only a flood of bugs that need to be fixed, be fixed, but I also hope it encourages people to switch.

    --

    ./revolution
  201. no, no, no and no! by Archimonde · · Score: 1

    It come up with Britney's last album.

    --
    Trolls are like broken clocks. They show the truth two times a day. The rest of the day they talk nonsense.
  202. MOD parent UP pls by Anonymous Coward · · Score: 0

    claryfying as hell

  203. Re:No original thought anymore. Fear! by Anonymous Coward · · Score: 0

    Yeah, no shit. He's backpedaling so far he can't keep up!

  204. Check your facts? by Xenographic · · Score: 1

    This is not an exploit, unless having the EIP register contain 0x44332211 does something more than just cause a crash. Now yes, that bitmap could be modified so that it's all NOPs followed by an actual exploit, but the one posted does no such thing.

    Did you RTFA?

  205. Re:No original thought anymore. Fear! by rjw57 · · Score: 1

    Dude, chill. Ride the /. comment wave. /Know/ that you are better don't lower yourself.

    *snigger* ints *snigger*

    cheek.remove(tongue);

    --
    Rich
  206. Re:I told Microsfot about this exploit two years a by Anonymous Coward · · Score: 0

    Offtopic my ass! Stupid fucking moderators!

  207. Yo, Tom by Anonymous Coward · · Score: 0

    When you find yourself in a hole, stop digging.

  208. Re:No original thought anymore. Fear! by tomstdenis · · Score: 1

    It's all from fucking ACs. I wish you could turn ACs off completely from /. that way I wouldn't have to see the nonsense of jackasses trying to give people a hard time over every little detail.

    Well go fuck yourselfs. You win. Here I'm giving up my /. account.

    The password will be "ihateac" in about 20 seconds. Enjoy the account folks!

    Tom

    --
    Someday, I'll have a real sig.
  209. Link to FICTION article. by Alsee · · Score: 1

    Note the last line which says Revised 27 June 2006 . Link is to a fiction piece.

    -

    --
    - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    1. Re:Link to FICTION article. by despik · · Score: 1

      It also says Using anything other than plain ASCII text on websites or in e-mail is a guaranteed way of terminating your net account, Sherlock. Of course it's a fiction piece.

      --
      "I seem to have mastered a certain amount of control over physical reality."
  210. The ultimate Windows exploit.... by Grog6 · · Score: 1

    ...a script that loads the Goatse.cx photo, makes it the wallpaper, sends it to everyone in your outlook express address book, and overwrites all your porn with tubgirl!! ...and then reboots the computer instantly everytime you try to load a floppy or cd or hit the internet....

    Man, talk about evil....

    --
    Truth isn't Truth - Guliani
  211. Exposing Your Identity by SAJChurchey · · Score: 1

    Isn't anybody worried about exposing themselves to the wrath of M$. Anybody who has this code is doing something illegal. Is it really intelligent to state that you have it on a public board or post security flaws and the source code you used to find it.

    What can M$ really do to people who have the code or spread the code farther?

    1. Re:Exposing Your Identity by gooman · · Score: 2, Funny

      You tell 'em. Someone called the cops the last time I exposed myself.

      --
      "Kittens give Morbo gas!"
  212. Has anyone determined how to test for this yet ? by Anonymous Coward · · Score: 0
    Given that there are many sites that allow users to post images or links to images (Ebay, Slashdot, etc) how would a site hosting such images check to determine that they were not being used by soneone to 'host' such images ?


    I hate to think of the havoc someone could cause by putting some appropriately constructed images on Ebay.

  213. Sure, they can say that by xant · · Score: 1

    But they can't argue that closed source as a strategy works. The source was leaked! Their strategy was unsuccessful, and may well be catastrophic for their customers as the thousands of unfixed bugs will now see the light of day.

    --
    It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
  214. Re:IE5.0 still accounts for the majority of browse by reso · · Score: 1

    Wow. That is interesting. You must remember to waste more of my life with your unsubstantiated, and somewhat useless "facts." Quite interesting indeed.

    My "website" logs show 72% MM 2.3 and 28% Web-n-Viewer 1.2

    I want my time back

    --


  215. Re:IE5.0 still accounts for the majority of browse by reso · · Score: 1

    "My logs show that 75% of the traffic to my website are from IE 5. The remaining 25% are IE 6.0 and Mozilla Gecko based browsers." that was who i was aiming at, not the people that posted useful info afterwards :)

    --


  216. Stolen? by gcore · · Score: 1

    How can this code be stolen? Doesnt MS have the code anymore? If someone stole my car i wouldnt care much if I still had my car. This IP-crap is soo boring But this is somewhat a good thing, it proves that Windows* is based on crappy code.

  217. Size of file? by Gorimek · · Score: 1

    From reading the notice it seems like the size of the bitmap has to be bugger than 2^31. That's over 2GB if my binary math is working right.

    If so, I doubt you'll get many people walking into a trap it takes hours or days to download.

    But maybe I misunderstand what the 2^31 means.

    1. Re:Size of file? by Anonymous+Squonk · · Score: 1

      2^31 bits would only be 2^28 bytes (since a byte is 2^3 bits), which would end up being a file a little over 500MB. If you convinced people that they were actually downloading a new Paris Hilton movie, they might be convinced to stick around long enough for that...

  218. IE6 is a free download by bonch · · Score: 2, Insightful

    You do realize IE6 is a free download for 98/2000 and up, don't you?

    If this were an OSS program, everyone on Slashdot would be falling over themselves posting to "upgrade to the latest version, it's fixed." But when it's Microsoft, suddenly there's some sort of unnamed hassle when it comes to just downloading a setup program and running it.

  219. And all my drivers would stop working by tepples · · Score: 1

    Linux fixes many problems but adds new ones, such as inability to talk to my Microtek 4850 scanner (unsupported in SANE CVS), inability to talk to my ATI Radeon 9000 video card in accelerated mode, inability to use Centrino winwifi chipsets, inability to talk to any of my relatives' dial-up providers (they're on AOL, MSN, and Juno), and several others that I'd have to dig up. Even printer drivers cost extra.

  220. Re: of been by Anonymous Coward · · Score: 2, Funny

    You of a keen wit.

    You're the sort have guy I admire.

    You could of noted the grammatical humor, but instead you chose to be have a cleverer sort.

    Shame about the lead paint in your nursery.

  221. There is... by Cyno01 · · Score: 2, Interesting

    The right combo of blinkenlights, color, speed, pattern etc can trigger a seizure in people even without epilepsy.

    --
    "Sic Semper Tyrannosaurus Rex."
  222. Re: most effective SPAM subject line? by Frankensloot · · Score: 0

    The "source code" of a book is the knowledge and work--arguably a lifetime of each--it took to produce the book. The "source code" of a newspaper might be the raw newswire feeds, newsroom banter, property and physical plant, etc. And most tellingly, the "source code" of that box of Frosted Flakes is not just the ingredients list. It includes the manufacturing process, for instance--how did you think the Coca-Cola formula is a secret if the ingredients are printed on every bottle and can?

    I hate analogies, anyway.

    It's just ridiculous to expect to receive the source code to every application you buy off the shelf and expect it to be free as in speech. (Which I realize may not be your position, but that was the original poster's argument.)

  223. WARNING: ARTICLE CONTAINS SOURCE CODE by Nailer · · Score: 4, Informative

    This is completely off topic from the parent post. But THE LINKED ARTICLE CONTAINS SOURCE CODE FOR WINDOWS.

    The Slashdot editors should remove the link immediately. Its really dangerous to have on the front page of this site.

    1. Re:WARNING: ARTICLE CONTAINS SOURCE CODE by Anonymous Coward · · Score: 0

      You read the article? Amature!

    2. Re:WARNING: ARTICLE CONTAINS SOURCE CODE by Anonymous Coward · · Score: 0

      I think the more important question (for maybe half the /. readers) is if the linked article contains links to a 'sample' exploiting bitmap...

    3. Re:WARNING: ARTICLE CONTAINS SOURCE CODE by Britz · · Score: 1

      I have been reading warnings like this in other stories about the source code leak on Slashdot as well.

      "Don't look at it, it will taint You and Microsoft will take over Linux!"

      Some even suggested that this is a plot by Microsoft to taint oss developers and later claim in court that Linux is now property of Microsoft.

      What has happened????
      The Slashdot crowed used to consist of people proud to wear decss t-shirts. Now all cowardly put their heads down and bow to Microsoft and its powerful lawyers wielding the DMCA.

      What happened to the country freedom of speech seemed so important?

  224. Re: most effective SPAM subject line? by Anonymous Coward · · Score: 0

    Yes, but some Windows users (like me) would rather live in ignorance. It's better not to know what is in it. Seriously.

  225. I wonder... by dfj225 · · Score: 1

    Maybe this should be an Ask /. question or a poll or something but I've been wondering about this for some time. If MS suddenly became open source, allowing users to download source for all of their programs would more people from this crowd support them? I'm not saying that MS necessarily give out their code under the GPL, but just allowing users access to it. I'm not even sure if any company uses a system like, and I suppose the best way to think about it would be like a book. Everyone can read it if they wish, but it is still copy righted and still illegal to reproduce it or to use portions of it.

    --
    SIGFAULT
  226. Profit by Anonymous Coward · · Score: 0

    1. load int from char array
    2. check int against sizeof(yourbuffer)
    3. reject if greater


    Heh! I kept waiting for someone to deliver the punch lines, but they weren't coming. So here they are:

    4. ???
    5. PROFIT!!

  227. Oooohhh the f@cking irony ! by garbagedisposal · · Score: 1

    http://slashdot.org/articles/02/06/04/228240.shtml ?tid=109

  228. maybe a stupid question by Dzerzhinski · · Score: 1

    . . . from a nonprogrammer, but does this vulnerability occur in the mac version of IE5 as well?

    --
    Never trust a physicist further than his DeBroglie wavelength.
  229. gcc -E by Anonymous Coward · · Score: 0

    resolve #defines before you search.

  230. MS crypto subsytem? by bigberk · · Score: 2, Interesting

    I wonder if any of the leaked source code includes the MS crypto system. If so, this could be very bad news for Microsoft seeing how people have already discovered a slew of critical vulnerabilities but are biting their tongues to wait for MS to fix the flaws. Now you have a bunch of crackers running their debuggers on actual source code... they are going to craft and use exploits before they're public knowledge or officially fixed.

  231. Re: Not running as Admin or Root != safe by Lord+Bitman · · Score: 1

    Should feel confident that IE doesnt have some back door? Did you not read the summary? :)

    Remember that many worms will simply go away when the computer is rebooted. There is no need for Admin Rights/Installation if you can just post a message on a popular site with an image in your signature.

    As for MacOSX, you may want to note that Microsoft did it first. That is, they made it an available option, and it's trivial to impliment. Programs don't always use that option, of course, usually (in my experience) waiting until an install is half-completed before noticing that admin rights are required, then telling the user to do it by hand. The option is available to developers, though. They can all check their privs and display a password box up front if they get off their asses.

    Of course, I wouldnt call such a thing "secure", since it then becomes trivial to distribute a program which prompts for administrative password, then says "incorrect password" and goes on to display the real password box. Later asking for an e-mail address, coupled with people tending to use the same password everywhere- well, making things easy and making things secure is always going to be a trade-off somewhere.

    Yeah, things arent destructive as much anymore, but I think most people would prefer ~/finance/ stays more secure than /etc/shadow (which, seriously, who gives a fuck about?)

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
  232. Good workaround for .BMPs, at least by Reziac · · Score: 1

    I decoded the BMP and loaded it into IE5.00.2314.1003 (the only IE version I consider worthy of disk space, if not safe to let run loose), completely forgetting that I had IE configured to use QuickViewPlus as the BMP viewer. IE dumped the file to QVP, which displayed it without incident. Hmm, well, so much for THAT test. :)

    The problem is... does this affect *all* bitmapped images, or only for-really BMPs? because it's not terribly practical to send *every* image to an add-on viewer.

    --
    ~REZ~ #43301. Who'd fake being me anyway?
  233. Yeah.... by Anonymous Coward · · Score: 0

    Has anyone ever thought that the first few exploits based on this 'leak' that will be reported arent just **** from people that figured it out back-in-the-day and are now posting to get the credit for it? Or maybe just steal the credit from someone else who originally figured it out?

  234. Re: Not running as Admin or Root != safe by chrootstrap · · Score: 1

    "Of course, I wouldnt call such a thing "secure", since it then becomes trivial to distribute a program which prompts for administrative password, then says "incorrect password" and goes on to display the real password box. Later asking for an e-mail address, coupled with people tending to use the same password everywhere- well, making things easy and making things secure is always going to be a trade-off somewhere."

    Hahah... you're keyed into one of the most serious security gaps in user habits: using the same password everywhere. This has really been compounded by the way so many websites require username/password. If joeblow/drowssap makes an account at mydumbsite.com and I can find anywhere else he has an account (e-mail, slashdot, ebay, paypal, ...) there is a reasonably good chance that the password will work. Of course, as you crack one thing you tend to learn more access; the webmail yields a power bill, etc.

    I personally believe in partitioning security into more than one level (analogous to guest/user/root) and then, of course, applying much stronger security (particularly encryption) up the chain. Of course, one of the things that helps with security the most is knowing what the heck the system is doing inside; there is a strong argument for having the source available right there. People who are blaming the author of the securityfocus submission are misplacing the responsibility for these security flaw. As I said, this very type of crack was something I was just thinking about last week; undoubtably many people have experimented with tainted BMPs, etc.

    We are fortunate to finally know about it, honestly! :)

    --
    Hacking articles at http://www.geocities.com/chroo
  235. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  236. I like it by scribblej · · Score: 2, Funny

    You said:
    There are also no exposed pointers in Java, thus no way to clobber the stack by writing to a negative array offset, as in this exploit. Reading or writing to a negative array offset in Java will result in a RuntimeException of some sort. Buffer overflows are also impossible in Java, since writing off the end of an array will result in a similar exception.

    I say:
    Yes, I agree completely. The next version of Windows should be written in Java.

  237. This is stupid by Moraelin · · Score: 1

    Just download IE 6 from Microsoft's site and there you go. MS even proposes that you do so every time you visit their update site.

    The exploit actually requires you to view a malformed bitmap. You won't find any such bitmaps on Microsoft's site, and you can't get hacked via some RPC port while you update.

    I.e., here's the deal, lemming: just click on that big "Microsoft upgrade" entry in the "Start" menu, and accept the proposed downloads. That's _all_ you need to do to fix this exploit.

    I.e., please spare me the stupidity of "what if I want to wait for a fix for an outdated version of IE instead of downloading the existing free upgrade?" You'd be just as vulnerable if you absolutely didn't want to upgrade from an ancient version of Mozilla. Which _did_ have a few exploits, in spite of being OSS.

    Either way, guess what? Even with Mozilla it's the same deal. You get to download a newer version.

    Or I can think of quite a bunch of equally critical fixes that a whole bunch of other OSS Linux programs needed, in every single distro I've used. Which, typically mean... guess what? That you have to get a newer version of that program.

    Yes, with you could personally fix every single bug in an ancient version of Sendmail, and Mozilla, and about 200 other ancient programs, if you really don't want to upgrade. But noone's going to do that. Why? Because reading and _understanding_ some 100 megabytes of source code, _and_ then fixing the bugs you've introduced while doing so, is _not_ going to be a $250 job. It's more likely going to keep a whole department busy making new bugs from now until kingdom come, and cost _millions_.

    Plus, much as MS bashing is fashionable and cool on Slashdot, we're talking the same crowd which absolutely must spend countless hours downloading and compile every single new release of KDE and/or Gnome and/or XFree86 and/or the weekly kernel release, etc. So it's downright stupid to now hear about how inconvenient it is to download an IE update. An update that's half the size of the 2.6 kernel bz2, and doesn't require any compiling either.

    --
    A polar bear is a cartesian bear after a coordinate transform.
    1. Re:This is stupid by God!+Awful+2 · · Score: 1


      I.e., please spare me the stupidity of "what if I want to wait for a fix for an outdated version of IE instead of downloading the existing free upgrade?" You'd be just as vulnerable if you absolutely didn't want to upgrade from an ancient version of Mozilla. Which _did_ have a few exploits, in spite of being OSS.

      *Current* versions of Mozilla routinely crash my browser when I view pages with various form elements. This is really annoying, because when I develop a web page, I have to test it not just on IE6, but on multiple versions of Mozilla to see if any of them are likely to crash.

      -a

  238. Linux Autoupdate Here ( RPM's only ) by f0rt0r · · Score: 1

    Say hello to my little friend Yum...
    http://linux.duke.edu/projects/yum/index.p tml

    --
    I can't afford a sig!
  239. FUCKING TROLLS! by jotaeleemeese · · Score: 2, Funny

    Of course you realize that it is absolutely pointless.

    If MS is doing its work they will check the exploit's code and fix it in a timely fashion.

    --
    IANAL but write like a drunk one.
  240. Patches... by jotaeleemeese · · Score: 1

    But just for the sake of argument, where would you get free patches for Red Hat 7.3?

    In the same place where you would get your patches for Windows 3.1.

    No wait, I could pay somebody to patch my RH system.

    Who is going to fix this hypotethical yours?

    --
    IANAL but write like a drunk one.
  241. Right. by jotaeleemeese · · Score: 1

    You either post the thing the way it is or you censor it because it is not PC. /. has to do a balancing act and in this case the decission is the correct one: this is worthwile talking about, so the puerile attitude of the poster can be put aside (without condoning it) for the sake of analyzing the information that is really important (the exploit).

    --
    IANAL but write like a drunk one.
  242. They use to have 40.... by jotaeleemeese · · Score: 1

    .... so maybe all is not that rosy after all?

    --
    IANAL but write like a drunk one.
    1. Re:They use to have 40.... by ipfwadm · · Score: 1

      I don't see where they used to have $40 billion in cash, looking at their annual reports going back to 1995. Maybe you're considering "short-term investments" as cash, which I was not. Cash + short term investments currently is $49 billion (which is still much more than for any other year since 1995).

  243. We are waiting. by jotaeleemeese · · Score: 1

    Linux has been here for many years, we are waiting.

    Oh wait, it is not that easy because the OS is of superior quality.

    OK, that is the end of your conspiracy theory.

    --
    IANAL but write like a drunk one.
  244. Exactly. by jotaeleemeese · · Score: 1

    Now I want to read all those advocates of thightly integrating an user space application like IE with the OS's kernel.

    For ages many people have tried to drive home in the MSofties' brains ahy this is a bad idea.

    Hopefully (unlikely) they will get it now.

    --
    IANAL but write like a drunk one.
  245. That's not unique... by Goonie · · Score: 1

    The open source project I used to work on had a "won't fix" category, as well as a "won't fix until the next major revision" category. The "won't fix" was for things that our opinion weren't broken, and the "won't fix till later..." were for issues that required major structural changes to fix.

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
  246. Jailbait idiots by Anonymous Coward · · Score: 0
    Why do people think that they can do this? Whoever is hosting that torrent should expect a knock on the door from the FBI any day now.

    BitTorrent is not anonymous, from a legal perspective, you may as-well just put it on your web server.

    1. Re:Jailbait idiots by Anonymous Coward · · Score: 0

      Agreed. This is a different kind of "security through obscurity". I guess they are just assuming that usoft is not going to go after every single person hosting the file, when there could be thousands. Posting the link on Slashdot does make them a bit less obscure though.

      Kazaa and Edonkey are not much better. Presumably it would take usoft some time to develop the infrastructure to automatically capture IP addresses of P2P sharers though. Those who want to share the files probably have at least a small window of opportunity. This is why, although I have no real interest in reading their code, even I am considering downloading it while it's still available.

      The most sensible place to share the Windows source (and it *should* be shared) is on FreeNet and GNUnet). Hell, if only because it will be a great test of these fledgling systems. Being FBI resistant is precisely what these systems were designed for.

  247. Re:Open S MOZILLA is the patch by bach37 · · Score: 1

    Not to mention [Mozilla is] not as mature as IE6.

    Man, you've got a lot of guts posting something like that on Slashdot.

    Next time don't forget to add the (/sarcasm) to the end of your post.

    Scott

  248. How does it feel to be owned so many times? by Anonymous Coward · · Score: 0

    You are the dumbest person I've seen in a long time. From your inane and unfactual Mac zealotry to your racism against minority groups, the stupidity never stops!

    What kind of dipshit thinks he can get away with posting pro-censorship opinions, get modded down to Terrible karma, and then thinks they can regain it?

    I saw your attempt to mod up your own comments. Luckily, I contacted Slashdot and had this situation taken care of as this is blatant abuse of the system.

    If you think you can get away with conning the readership here, you are insane beyond your own stupidity.

    Give up! You're a moron! You have no clue or chance! You're like the little dipship kid who wants to leech off of everyone in life and then cries when he doesnt get his way.

    GO AWAY, LOSER.

  249. Some people can't upgrade to IE 6 by metamatic · · Score: 1

    If your company was dumb enough to build for a specific browser rather than following web standards, you can't always replace IE 5 with IE 6 and have your web sites still work.

    For example, IE 6 removed support for some plugins, and now comes without support for Microsoft's broken Java 1.1.8 VM.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  250. I wish I had some mod points... by metamatic · · Score: 1

    ...but I don't know whether I'd rate that as funny, insightful, or a sad reflection on the industry I work in...

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  251. Re:No original thought anymore. Fear! by Krusty_Klown · · Score: 1

    I know this is old but, hell ya! Mr. manic depressive is gone!