Slashdot Mirror


Microsoft to Patch WMF Exploit Early

Chran writes "Microsoft has just announced that they will release a security update for the .WMF-exploit today at 2pm ET, instead of Tuesday, as originally planned. Microsoft writes: "Microsoft originally planned to release the update on Tuesday, January 10, 2006 as part of its regular monthly release of security bulletins, once testing for quality and application compatibility was complete. However, testing has been completed earlier than anticipated and the update is ready for release. In addition, Microsoft is releasing the update early in response to strong customer sentiment that the release should be made available as soon as possible."

306 comments

  1. Reactive vs Proactive by biocute · · Score: 5, Insightful

    Microsoft is releasing the update early in response to strong customer sentiment that the release should be made available as soon as possible.

    It would have been nicer if they make patches available as soon as possible with or without strong customer sentiment.

    1. Re:Reactive vs Proactive by Anonymous Coward · · Score: 0

      Its available via windows update. Good Luck!

    2. Re:Reactive vs Proactive by Anonymous Coward · · Score: 5, Informative

      Patch has been released.
      Get it here http://www.microsoft.com/technet/security/Bulletin /ms06-001.mspx

      According to the folks at F-secure, it co-exists well with Ilfak's unofficial patch as well as the REGSVR32 workaround. Read their blog here. http://www.f-secure.com/weblog/archives/archive-01 2006.html#00000771

    3. Re:Reactive vs Proactive by cnettel · · Score: 5, Interesting
      For an out-in-the-wild exploit, I would agree. For one that is currently, to their knowledge, not known among the script kiddies of the world, I'm not so sure. Releasing a patch will, generally, make those who are not yet prepared to implement it more vulnerable, if it means that knowledge of details is more wide-spread.

      I think that some corporate users (especially) are quite thankful for patch Tuesdays; especially those that have been bitten by some compatibility issue previously and can't just run autoupdate of all desktops at night, but rather want to roll it out manually.

      Again, this is not the case here, this exploit was discovered in the wild and it's spreading right now.

    4. Re:Reactive vs Proactive by targo · · Score: 3, Insightful

      It would have been nicer if they make patches available as soon as possible with or without strong customer sentiment.

      This doesn't make any sense. All patch release dates are a function of:
      1) impact of the problem
      2) complexity of required testing
      The idea being that the patch shouldn't cause more harm than the original flaw.
      If the impact is huge, testing of more obscure cases can be deferred somewhat. If the impact is small, more time can be taken.
      So if there hadn't been any customer sentiment (i.e. no one cared), it would make no sense to rush the patch and risk breaking something.

    5. Re:Reactive vs Proactive by lord_rob+the+only+on · · Score: 1

      Yeah and a quickly made patch generally is a bad patch, some kind of a hack that doesn't really fix the cause of the problem.

      That said, I don't know for that particular case, I just say that in general (and this rule has been proved right many many times for Micorsoft products).

    6. Re:Reactive vs Proactive by thefogger · · Score: 1

      Microsoft releases updates on "patch tuesday" as opposed to "as soon as possible" because admins asked for easier planning of downtimes. They're releasing this patch now, because their customers consider it to be extremly critical. Where's the problem?

      --


      Um... I didn't do it!
    7. Re:Reactive vs Proactive by Tony+Hoyle · · Score: 1

      It's easy for admins to plan their downtimes unless they have windows update run automaticaly every day or sometinh - there is even a tool that lets admins collect patches and roll them out locally on a schedule (although it needs a dedicated machine and insane amounts of resources... the minimum is 512MB and it isn't happy in less than 1GB, so many admins understandably can't run it due to hardware/budget limitations).

    8. Re:Reactive vs Proactive by grcumb · · Score: 4, Insightful

      "If the impact is huge, testing of more obscure cases can be deferred somewhat. If the impact is small, more time can be taken."

      I'm with you so far....

      "So if there hadn't been any customer sentiment (i.e. no one cared), it would make no sense to rush the patch and risk breaking something."

      Err, that's a non-sequitur. Whether customers care or not has nothing to do with the cost/benefit analysis that decides the timing and scope of an initial patch. A software company should never rely on its customers to perform risk analysis. If it's serious (and the WMF flaw is egregiously so), then you find a way to protect your customers as quickly and effectively as you can. In some cases - though certainly not all - you can even accept shortcomings in the patch itself if significantly reduces the risk.

      The third-party patch, for example, causes issues with the Windows printing subsystem. People voiced suspicions that this might be the case right from the start, though confirmation only came through earlier today. To my mind, that was an acceptable risk. A server that can't perform some print tasks and won't show pretty preview icons is worth a heck of a lot more to me than one that's 0wned by some random script kiddy.

      And before some astroturfing twit spouts the simplistic, binary logic of 'MS is damned if they do and damned if they don't', I'd like to say from experience that deciding the timing of a security patch is a terribly difficult process. It requires the right amount of analytical skill, deep technical expertise, a healthy dose of horse sense and exactly the right measure of patience. Too much or too little of any of these can result in exactly the wrong kind of response.

      Patching is not about being a nice guy. It's not about what your customers think of you. There should be no marketing or sales angle in the creation or timing of a security patch. You determine the scope and severity of the threat, be as thorough as you can reasonably hope to be (and that's never as thorough as you'd like), and deliver it as soon as you reasonably can.

      I'm in complete agreement with this handler's diary from isc.sans.org concerning Microsoft's announcement that they would issue the patch at the regularly scheduled time. Given the severity of the flaw, it's unconscionable that they should leave their customers exposed for so long. The fact that they only decided to release the patch out of cycle in response to their users demonstrates that they're far more worried about their image than they are about their software. This does not bode well at all for them. Or for their customers, for that matter.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    9. Re:Reactive vs Proactive by Heembo · · Score: 1

      So 8 days after this specific vulnerability was discovered, MS send out a patch after a complete regression-test in 23 languages (or so). I say, a decent response. Not great, but not terrible, not totally irresponsible. Will be interesting to listen to the techcast from MS tomorrow. But in general, this is just yet another example as to why my favorite MS patch is what Johannes Ullrich calls "the Fedora Patch".

      :)

      --
      Horns are really just a broken halo.
    10. Re:Reactive vs Proactive by Anonymous Coward · · Score: 0
      Yeah and a quickly made patch generally is a bad patch, some kind of a hack that doesn't really fix the cause of the problem.


      Noone seemed to mind when it was unofficial patch, and noone would care if such a kludge made it out in the Linux kernel?
    11. Re:Reactive vs Proactive by jatemack · · Score: 2, Informative

      it co-exists well with Ilfak's unofficial patch as well as the REGSVR32 workaround.

      And if you did the REGSVR32 workaround, you can now get back the functionality of Windows Picture and Fax viewer.
      Click Start, Run, Type "regsvr32 %windir%\system32\shimgvw.dll" (without the quotation marks) then OK.

      This info was kind of buried here.

      --
      // no
    12. Re:Reactive vs Proactive by Anonymous Coward · · Score: 0

      They used to. Then they switched to the monthly rollout after people were tired of reinstalling WinXP Gold and having to install 65 updates and a service pack or two. They finished testing early (dubious), and decided to release a critical patch early like they occasionally do. Can't fault them for their timing, just fault them for holes and the inability to release stable cumulative patches that would just be one giant download (which they are slowly coming to).

    13. Re:Reactive vs Proactive by drsmithy · · Score: 1
      It's easy for admins to plan their downtimes unless they have windows update run automaticaly every day or sometinh - there is even a tool that lets admins collect patches and roll them out locally on a schedule (although it needs a dedicated machine and insane amounts of resources... the minimum is 512MB and it isn't happy in less than 1GB, so many admins understandably can't run it due to hardware/budget limitations).

      Rubbish. It runs quite happily on a multipurpose machine. For small shops, the fileserver or one of the domain controllers would be a reasonable choice.

  2. and millions of /.'ers groan... by B00yah · · Score: 5, Funny

    Thank you for your interest in obtaining updates from our site.

    To use this site, you must be running Microsoft Internet Explorer 5 or later.

    To upgrade to the latest version of the browser, go to the Internet Explorer Downloads website.

    1. Re:and millions of /.'ers groan... by Foofoobar · · Score: 0, Troll

      Well the funnt thing is that this exploit only affects Internet Explorer as well. Si basically what they are saying is:

      'In order to patch for this exploit, please first make yourself vulnerable for a solid kick to the nads.'

      --
      This is my sig. There are many like it but this one is mine.
    2. Re:and millions of /.'ers groan... by winkydink · · Score: 1

      If you haven't been there since IE 5 was current, you're going to be a while.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    3. Re:and millions of /.'ers groan... by ergo98 · · Score: 3, Insightful

      Well the funny thing is that this exploit only affects Internet Explorer as well. So basically what they are saying is

      They aren't "saying" anything. The Windows Update web app, as a requirement of the fact that it uses ActiveX, requires Internet Explorer. Nonetheless, not only is the patch rolling out right now via auto-updates, you can also download it directly.

      In any case, even though I use Firefox and Opera for my day to day browsing, I really don't feel that threatened firing up Internet Explore for the purpose of connecting to Microsoft.

    4. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      Duh.... it's their deviation from standards that keeps making them vulnerable. ActiveX is more a security flaw than a feature and it's their choice to continue to try and force it down peoples throats thatn attempt to conform with industry/w3c standards.

      Regardless, it's a catch-22. Here's the patch to keep you from being vulnerable but you must be vulnerable in order for us to patch. Gotta love the rocket scientists Microsoft is hiring these days.

      --
      This is my sig. There are many like it but this one is mine.
    5. Re:and millions of /.'ers groan... by SirDaShadow · · Score: 2, Informative

      go get the IEtab extension for Firefox and whitelist update.microsoft.com to use the IE engine instead of the gecko engine and viola...

    6. Re:and millions of /.'ers groan... by Mr.+McGibby · · Score: 1

      Gotta love the rocket scientists Microsoft is hiring these days.

      Rockets! Awesome. Some real money finally being invested in space.

      --
      Mad Software: Rantings on Developing So
    7. Re:and millions of /.'ers groan... by ergo98 · · Score: 2, Insightful

      Duh.... it's their deviation from standards that keeps making them vulnerable. ActiveX is more a security flaw than a feature and it's their choice to continue to try and force it down peoples throats thatn attempt to conform with industry/w3c standards.

      Conform with industry standards? What sort of nonsensical groupthink claptrap is that? Is there a W3C standard on updating system libraries via a webpage that Microsoft isn't conforming to? Right - no there isn't, and ActiveX exists as embedded content just like Flash, Java, and many other non-W3C technologies, as it should.

      As mentioned, though - THERE ARE TWO OTHER AVENUES FOR GETTING THE PATCH, rendering your original comment ridiculous at the outset.

    8. Re:and millions of /.'ers groan... by ivan256 · · Score: 1

      ActiveX [...] requires Internet Explorer

      Says who?

    9. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      Well the funnt thing is that this exploit only affects Internet Explorer as well.

      No, it affects Windows. Your browser choice doesn't matter. Also, if you don't type so fast, you won't make so many errors.

    10. Re:and millions of /.'ers groan... by Foofoobar · · Score: 0, Flamebait

      It doesn't exist because everyone with a brain knows it's not needed to be a standard. ActiveX was completely rejected because it creates one giant security hole straight to the OS in Microsoft's case. And jthe vast majority of holes in IE have been a direct result of ActiveX.

      There's a reason why these people are in charge and not you. They're smart :)

      --
      This is my sig. There are many like it but this one is mine.
    11. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      As mentioned, though - THERE ARE TWO OTHER AVENUES.........

      that is 100% correct

      www.SimplyMEPIS.org
      1) download ISO
      2) burn ISO to CD
      3) reboot using CD
      4) click "Install Me" icon on desktop
      5) format with "Use Entire Drive"

    12. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      Can I be the first to say 'eeeeewwwwwww!'.

      Yes please, I'd like to add a giant security hole to my browsing experience thank you very much. Where do I sign up?

      --
      This is my sig. There are many like it but this one is mine.
    13. Re:and millions of /.'ers groan... by EvanED · · Score: 1

      But it does matter, because if you load a page in IE that has a WMF image in it IE will display it, while FF will not. Hence you can have a problem by simply opening a page if you use IE, but not FF. (Or at least this is my reading.)

      But you're right, it's a Windows bug, not an IE bug, and if you were to download a malicious WMF in FF and open it in most any program you'd have a problem.

    14. Re:and millions of /.'ers groan... by ergo98 · · Score: 0, Flamebait

      There's a reason why these people are in charge and not you. They're smart :)

      Are you 12? Seriously. Not only are you incredibly juvenile, but your ignorance is extraordinary.

    15. Re:and millions of /.'ers groan... by l1_wulf · · Score: 4, Informative

      Actually, the only reason IE is vulnerable but FF & Opera is not, is because the other big name browsers associate WMF files with Media Player instead of Picture and Fax viewer. WMP does nothing with WMF files, therefore nothing happens when exposed to the vulnerability. On the other hand, should the offending graphic actually get on your hard drive and you use Google Desktop, you will be vulnerable due to the indexing done immediately after download (obviously, if you have indexing turned off for graphics, this won't happen).

    16. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      Wow! Way to counter my point. The 'you must be 12' defense. I know I'M convinced!

      --
      This is my sig. There are many like it but this one is mine.
    17. Re:and millions of /.'ers groan... by TuneShark · · Score: 2, Informative

      I went here for using firefox, followed a few links, and was allowed to download and install the patch:

      http://www.microsoft.com/technet/security/Bulletin /ms06-001.mspx

    18. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      What do you think of FireFox extensions?

    19. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      Since Firefox is sandboxed and not integrated into the OS, the riskj it poses is minimal. But their is a chance that you can download an extension from a site not approved by the Mozilla foundation juist as you could with a WORD addon, IE addon or any other plugin for software out there.

      Still alot safer than IE.

      --
      This is my sig. There are many like it but this one is mine.
    20. Re:and millions of /.'ers groan... by jonbryce · · Score: 1

      ActiveX lets a website look at what is on your computer and change things.

      Usually that isn't a good idea, but for WindowsUpdate, it is kinda necessary.

      On Mandrake, I have to use a separate program to do updates to my system. I don't really have a problem with the idea that Windows is like that as well.

    21. Re:and millions of /.'ers groan... by eatmadust · · Score: 1

      true, but you can rename the file exploit.wmf to exploit.jpg. Firefox will try to display the jpg and will pass the picture to the library, which will realize that it is incorrectly named and it will render it as wmf, infecting your system. This bug affects all browsers, whether they can display wmf's or not!

    22. Re:and millions of /.'ers groan... by cnettel · · Score: 4, Informative

      I'm not so sure about that. Yes, some picture loading libraries provided in Windows will do this. No, LoadBitmap won't (it's not a bitmap!). IIRC, Firefox doesn't use the same high-level libraries, as they are rolling their own code on all platforms. So, no, it won't happen. You can easily try this if you have a valid WMF file lying around. Rename it to JPG and open in FF. It won't render, complaining about an invalid header. Rename a valid PNG to JPG or a valid JPG to PNG, though, and it renders just fine. Firefox does auto-detection of image type, but not autodetection of WMF.

    23. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      Firefox is sandboxed??? On the "IE integrated into OS retoric" (the only thing it's ever been, useful for MS lawyers and people that either doesn't know any better or spreads the myth as fud because of an agenda) see this post.

    24. Re:and millions of /.'ers groan... by RemovableBait · · Score: 1

      Sorry, but I'd rather stick with something like this. It's the difference between swapping the rendering engine temporarily when required (eg. Windows Update) a shoehorning a massive security hole into Firefox. Your call :)

    25. Re:and millions of /.'ers groan... by drsmithy · · Score: 1
      Since Firefox is sandboxed and not integrated into the OS, the riskj it poses is minimal.

      1. Firefox is not sandboxed.

      2. Firefox runs at the same privilege level as IE (in other words, the user's).

    26. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      So are the rest of us. He's right, isn't he?

    27. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      IE's underlying
      engine runs as SYSTEM... which has higher levelk permissions than an administrator.

      How does Firefox have the same privileges?

      --
      This is my sig. There are many like it but this one is mine.
    28. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      Oooh... and another zinger from an anonymous troller. Let me know when you've figured out how to make an account and then come back and play with the big boys.

      It's always funny when you guys troll when you don't even have street cred. :)

      --
      This is my sig. There are many like it but this one is mine.
    29. Re:and millions of /.'ers groan... by drsmithy · · Score: 1
      IE's underlying engine runs as SYSTEM... which has higher levelk permissions than an administrator.

      No, it does not.

    30. Re:and millions of /.'ers groan... by twaltari · · Score: 1

      Actually IE is vulnerable, not because of associating WMF to Image & Fax viewer application but because IE automatically renders WMF by itself. Thus IE is exploitable even with a few lines of JavaScript that dynamically creates a WMF image. FF & Opera have no support WMF rendering. They do not try to automatically show WMF but pop up the "Save As / Open With" dialog.

    31. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      or you could just do the insane thing and use IE for windowsupdate :)

    32. Re:and millions of /.'ers groan... by Mortimer82 · · Score: 1

      Actually, I obtained this update, along with all other critical updates in the past without needing to fire up Internet Explorer. The URL mentioned in the article will allow me to download the patch with Firefox, whis was not necessary though as my "Automatic Updates" service prompted me almost as soon as I turned on my computer to apply this update.

      So, one does not *need* Internet Explorer for critical updates. Also, to be honest Internet Explorer is only potentially dangerous to use on untrusted websites or already compromised machines, so if you are using Windows, you have Internet Explorer anyway, so there is nothing wrong with using it for Windows Update, as long as you haven't already got malware from using it to browse some dodgy site.

      Honestly, I don't understand the complaint people have of only IE allowing them to obtain Windows specific software, Microsoft makes Internet Explorer freely available to whoever may need it for that purpose, and if it's got other problems (like already malware infested), use Firefox or something to download the patches manually.

    33. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      And you just keep on proving it.

    34. Re:and millions of /.'ers groan... by deaddrunk · · Score: 2, Interesting

      Is there away for a non-privileged user to receive notifications of new updates. I only knew about this one because it was so widely publicised. I know I can just log on as super-user first when I start my machine but I'd prefer to just have the notification before I have to log on to the super-user account.

      --
      Does a Christian soccer team even need a goalkeeper?
    35. Re:and millions of /.'ers groan... by ivan256 · · Score: 1

      Actually, I prefer neither.

      I have yet to find a site that I care about that isn't useable with Gecko.

    36. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      "IE's underlying engine runs as SYSTEM... which has higher levelk permissions than an administrator."

      You are a completely clueless twit. I'd advise just keeping your mouth shut, because everything you say just makes you look more uninformed.

    37. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      Street cred? You sound like a retard. I bet foofoobar is a name that makes bloods and crips alike tremble.

    38. Re:and millions of /.'ers groan... by Foofoobar · · Score: 1

      And you know what retards sound like from hanging at home or listening to your own voice?

      You anonymous trollers are too easy.

      --
      This is my sig. There are many like it but this one is mine.
    39. Re:and millions of /.'ers groan... by Anonymous Coward · · Score: 0

      "I really don't feel that threatened firing up Internet Explore for the purpose of connecting to Microsoft."

      Have you read their EULA and privacy policy? With about 10-20 different types of information they inform you will flow from your computer to Microsoft during the update process, and since Win2K they stopped using the "no personally identifiable information will be sent" phrase and just started scanning your computer for software and posting it all off to Redmond.

    40. Re:and millions of /.'ers groan... by Bert64 · · Score: 1

      Your right, firefox uses it's own cross platform image libraries...
      This is why firefox can display PNG images properly, while IE cannot. If they both used the same library functions, firefox couldn't display PNG properly either.
      If it encounters a file type it doesn't understand, it will offer to use an external program to view it, or save it, but it prompts you.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  3. Feh ! by witte · · Score: 5, Funny

    No problem... there's plenty of other exploits for windows.

    1. Re:Feh ! by Drew+M. · · Score: 1

      There sure are:
      http://www.eeye.com/html/research/upcoming/index.h tml

      This list alone shows 4 unpatched "Severity: High (Remote Code Execution)" issues

  4. whatever by TheRealMindChild · · Score: 3, Funny

    testing has been completed earlier than anticipated

    Sure.

    --

    "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    1. Re:whatever by Anonymous Coward · · Score: 1, Funny

      PROD: Hey, did that patch work.
      QA: What patch?
      PROD: The .WMF patch
      QA: Uh, yeah.
      PROD: Really. That was fast.
      QA: Yeah, well you know..
      PROD: Right, so we can release this early?
      QA: Sure, go ahead. I'll be working at google as of next week anyway..

    2. Re:whatever by gbobeck · · Score: 1

      Thats what Microsoft customers are for... testing MS code after QA finishes.

      --
      Navicula hydraulica plena anguilarum est. Omnes castelli tuus nostri sunt. Ed elli avea del cul fatto trombetta.
  5. Splendid... by Hymer · · Score: 4, Insightful

    ...only 10 days too late...
    ---
    tis is not a FP

    1. Re:Splendid... by cnettel · · Score: 1

      A few days earlier than they were notified about it, and before even the first /. duping? Nah, then Zonk and Taco couldn't outpost each other...

    2. Re:Splendid... by NothingMore · · Score: 1

      This was actually extremely fast for a vunlerbility in a major component for an operating system. If linux had a security hole of simmilar magnitude it probablly wouldent be patched this fast.

    3. Re:Splendid... by Anonymous Coward · · Score: 0

      If linux had a security hole No, probably not... IF it had...
      ...but FOSS don't have chair-throwing maniacs so they have the time to think how to make the best & most secure product instead of thinking about a deadline defined by a PR guy...
      --
      I am not a FOSS developer, I'm not good enough to be one...

    4. Re:Splendid... by Anonymous Coward · · Score: 0

      Whatever. Troll.

    5. Re:Splendid... by Anonymous Coward · · Score: 0

      SHUT THE FUCK YOU YOU FUCKING OSS FAGGOT I'm really sorry that your ass hurt so much after our interaction... It really wasn't my intention.
      2006 is year of Linux on the desktop right? Right? No, the year of the Linux on the desktop was in 2004... I'm sorry you poor bastards didn't get the message... or didn't you listen ?
      --
      This is an automatic troll responder message.
      Responses to this message will by ignored.
      <Resp.ID: 70F9-1B2F-CDCF>

  6. 3rd person by kennygraham · · Score: 5, Funny
    Microsoft writes: "Microsoft originally planned...
    kennygraham is glad that they're patching it early.
    1. Re:3rd person by ch-chuck · · Score: 1

      Then Bill Gates said, "Bill doesn't like high profile vulnerabilities", as he sacked three red-shirted employees.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    2. Re:3rd person by Ctawp · · Score: 1

      Uh oh. Urban self reference in the third person? Next thing you know their slogan is going to be "We're loving it" and they're going to launch a horrible ad campaign.

  7. 8 Days to patch by badriram · · Score: 3, Insightful

    Maybe it is just me, but 8 days for a tested patch does not seem that long. However it was a 0 day which made this exploit special.

    1. Re:8 Days to patch by Anonymous Coward · · Score: 5, Insightful

      ProTip : If a third party can patch it faster than you, without access to the original source code - you suck.

    2. Re:8 Days to patch by graphicartist82 · · Score: 1

      That doesn't necessarily mean that they regression tested the patch as microsoft would; that just means they created a patch and got it out faster.

      I'm sure it didn't take microsoft very long to create the patch, but lots of manhours to test it -- whatever that's worth.

    3. Re:8 Days to patch by MatD · · Score: 5, Funny
      I'm a third party, and I can patch it right now without even touching the code. Just beat your hard drive with a hammer, and you will be immune to the exploit.

      I have no idea what the side effects of this will be for your other applications (because I didn't do any regression testing), but I'm not MS, so I don't really care. Mat

      --
      Since when did operating systems become a religion?
    4. Re:8 Days to patch by croddy · · Score: 5, Insightful
      1. Release patch 8 days late
      2. Describe it as an "early" release
      3. ???
      4. Profit!!!
    5. Re:8 Days to patch by flynt · · Score: 2, Informative

      The third party patch didn't actually (AFAIK) patch the file in the operating system. It simply blocked the calling of the Escape() function, which broke printing on several machines and programs. So while a decent workaround for this week, it really isn't a long term solution. I got this information from SANS' ISC.

    6. Re:8 Days to patch by chunews · · Score: 1

      I would agree, if the 3rd party patch didn't have any side effects like affecting printing. For example.

    7. Re:8 Days to patch by rabtech · · Score: 1

      Patches need to follow the "do no harm" mantra... you don't want to make things worse by issuing an untested patch. How many resources does it take to ensure, within 8 days, that the patch doesn't break any of the patched versions of Windows, doesn't expose any NEW security holes, and doesn't break any known applications?

      --
      Natural != (nontoxic || beneficial)
    8. Re:8 Days to patch by chunews · · Score: 1

      Additionally, one cannot simply "throw more resources" at the problem to make testing go faster. Ie: I would shudder to think of the quality issues by asking marketing to get involved in regression testing because "we have to ship this out" -- the time it takes to labotimize, err, "train" the new individual may be more than simply doing the act yourself. Nobody (on ./) likes it, but Microsoft did a decent job of handling the situation. Not the best job, but a decent one.

    9. Re:8 Days to patch by Anonymous Coward · · Score: 0

      WOOOO!!!!! your better than microsoft.... :/ although, if you think about it, its pretty hard to be worse

    10. Re:8 Days to patch by RaffiRai · · Score: 1

      That's inane, goes knows how many exploits that ARE found inside of microsoft before they are outside, and patched without anyone ever knowing about it. 10x, 100x, 1000x? The idea that a few get past is unescapable.

    11. Re:8 Days to patch by TubeSteak · · Score: 4, Funny

      Your method sounds pretty easy.

      Do I have to reboot afterwards?

      --
      [Fuck Beta]
      o0t!
    12. Re:8 Days to patch by m95lah · · Score: 1

      No.

      Your computer is now safe.

      No infection whatsoever will affect it, except maybe rust...

    13. Re:8 Days to patch by Anonymous Coward · · Score: 0

      Is it just me, or does anyone else have problems with the term 'early' when this flaw affects versions of Windows shipped since 1990????

    14. Re:8 Days to patch by Minwee · · Score: 1

      However after this revolutionary process nothing, and I mean nothing, not rust, not mold, not even a nuclear blast, will reduce the performance and usability of your computer.

    15. Re:8 Days to patch by 10101001+10101001 · · Score: 2, Insightful

      >>It would have been nicer if they make patches available as soon as possible with or without strong customer sentiment.

      >Maybe it is just me, but 8 days for a tested patch does not seem that long.

      Eight days to test a patch might not be long, but if after you've tested it for 8 days you decide to delay releasing the patch for 10 more days to make it easier on consumers, then you've got to recognize that you've got a pretty major problem that a) you're patching so often that such is an issue and b) your patching mechanism is so bad it's such a hassle to apply patches.

      >However it was a 0 day which made this exploit special.

      Actually, there's a major problem with that mentality. How do you know that this exploit is special? For all you know other exploits MS is sitting on and already has a tested patch for are being exploited *right now*. Even worse, because you've deluded yourself into believing that you not hearing about an exploit from the press pre-patch release means you can apply the patch without worry that your box isn't already rooted.

      Of course, most people don't do a clean install over any patch, even if they're exploited by some program, unless it's utterly apparently necessary (ie, your computer is crashing so often you simply can't do anything). Why? Again, because it'd be such a hassle. Considering how many companies use Windows machines as front-ends to all sorts of data they probably don't want leaked out, it's amazing that Windows machines are even still accepted, regardless of how "necessary" Windows is. I guess it'll take a few high-profile cases of corporate espionage through non-press announced 0-day exploits for things to change.

      Oh, and just to make it clear, this is just as much a problem in Linux. The biggest advantages Linux and any open source OS have going for them are they can be trimmed to a very minimal set of files, which reduces the chances of containing an exploitable file let alone providing a means to exploit it. The long term answer is probably verifying software, much like how OpenBSD was auditted multiple times. If I were a company, I'd really look into OpenBSD over all OSs.

      --
      Eurohacker European paranoia, gun rights, and h
    16. Re:8 Days to patch by AmberBlackCat · · Score: 0, Flamebait

      If it were Firefox, you'd be praising them for releasing a patch so fast. And you'd be downloading 16 megabytes just to patch one little obscure feature. I know Microsoft is the devil but they do get some things right.

    17. Re:8 Days to patch by eyeye · · Score: 2, Informative

      If it were Firefox, you'd be praising them for releasing a patch so fast. And you'd be downloading 16 megabytes just to patch one little obscure feature

      Why would you download Firefox three times?
      --
      Bush and Blair ate my sig!
  8. is their face red by zietlow · · Score: 5, Funny

    "in response to strong customer sentiment" Ie we look foolish that the community was able to fix it sooner than we were. Here you go, we're not that bad afterall, see?

    Let's be friends again.

    --
    Slashdot # 199661 the number that's the same upside down and right side up
    1. Re:is their face red by cnettel · · Score: 1

      Only if the real fix is such a "shut the thing off" workaround as both the unregistering and real unofficial GDI disabling patch was, which both disabled a lot of valid cases.

    2. Re:is their face red by Anonymous Coward · · Score: 1, Interesting

      According to http://www.grc.com/sn/notes-020.htm, Microsoft actually patched this thing on December 28th. The built and digitally-signed GDI32.DLL carries that date.

    3. Re:is their face red by Sheepdot · · Score: 2, Informative

      Regarding the third-party patch...

      I simply unregistered the dll file on both work and home XP computers, but not the others I help supervise. The folks that are concerned about hackers "re-registering" it are working with the assumption that there is either another 0-day exploit out there that allows the hackers to do that, or don't understand how the vulnerability works. Also, the need for a patch on Windows 98, NT, or 2K is non-existant.

      I honestly think relying on a third-party to patch a system is ridiculous. Someone could tell me there is absolutely no ill-intent on behalf of the person releasing the particular patch, and even tell me exactly what the patch does. I still wouldn't implement it. The reason, of course, is because in five years, Microsoft will still be Microsoft, whereas Ilfak Guilfanov might disappear or ignore requests for help. Who knows if he'll even be contactable?

      Also, FYI, this specific "patch" he created hides windows functionality on a kernel level. There are other pieces of software that use this same kind of methodology: rootkits. While this could be considered a white-hat rootkit, it's just not a legitimate fix for the real problem. Unregistering the dll was the best solution for security nuts.

      Accountability is a very important factor. Microsoft might be taking a gamble on not releasing an insta-patch that breaks (what amounts to being) unused functionality at the cost of security, but that is their perrogative. Home consumers, and their other clients, get to be the judge on whether or not they are doing the right thing. By releasing this patch early, I think they've quelled some corporate concerns.

    4. Re:is their face red by Kris_J · · Score: 2, Insightful

      You are confusing accountability with ability. When the ideal situation does not exist, both must be considered.

  9. It's already out.. by Anonymous Coward · · Score: 2, Insightful

    http://www.microsoft.com/technet/security/Bulletin /MS06-001.mspx

    WSUS picks it up on synch so start deploying once you've tested it internally. 5 days early? Not bad. Not great, but an official patch is always welcome. Hats of to the SANS team for applying the pressure. It's unfortunate that they were not mentioned in the Acknowlegements section of the MS06-001 release notes.

  10. So early? by flicken · · Score: 4, Funny

    They would have released it earlier, but their test machines kept getting hacked...

    --
    20 mil and I will! Learn Esperanto with 20M others.
  11. WMFHotfix by Anonymous Coward · · Score: 0

    Figures it comes out the day after I patch all the machines with the unofficial patch. Any idea of compatibility? Install microsoft's patch then remove old patch?

    1. Re:WMFHotfix by ThoreauHD · · Score: 1

      Same here. The previous hotfix is uninstallable, but I'm wondering who I trust more. Microsoft or an IDS expert.. Decisions.. decisions.

    2. Re:WMFHotfix by novocastrian · · Score: 1

      The ISC has clear instructions on how to remove the unofficial patch, although it apparently co-exists ok with Microsoft's patch.

    3. Re:WMFHotfix by baadger · · Score: 1

      Add/Remove Programs -> Remove the unofficial hotfix first and then reboot, this'll totally clear the unofficial hotfix from memory (it's a runtime patch not an on disk fix).

      THEN install the official patch.

  12. Site's not Firefox-compatible by Anonymous Coward · · Score: 0, Flamebait
    Here is what the site looks like in Firefox:
    Thank you for your interest in obtaining updates from our site.

    To use this site, you must be running Microsoft Internet Explorer 5 or later.

    To upgrade to the latest version of the browser, go to the Internet Explorer Downloads website.
    The second question is this: Will Microsoft allow cheap-ass criminal software pirates like myself to use this patch? There are arguments both for and against allowing this patch to be used on pirated copies of Windows. The pro is that, pirated or not, a compromised system is a menace to the internet at large. To con is that Microsoft really ought to be paid whenever someone uses Windows, and people who steal Windows don't have the right to get patches.

    Of course, if Linux became the mainstream desktop OS, this would be a non-issue.
    1. Re:Site's not Firefox-compatible by Anonymous Coward · · Score: 0

      Of course, if Linux became the mainstream desktop OS, this would be a non-issue.

      You're right! That's because nobody could figure out how to patch their machines int he first place!

    2. Re:Site's not Firefox-compatible by Decaff · · Score: 1

      You're right! That's because nobody could figure out how to patch their machines int he first place!

      Er - have you used a mainstream linux desktop distro recently? It is like .... 'click on the update icon and wait'...

    3. Re:Site's not Firefox-compatible by slashnik · · Score: 1

      Of course, if Linux became the mainstream desktop OS, this would be a non-issue.

      You're right! That's because nobody could figure out how to patch their machines int he first place!

      Thats how it works in XP, and what percentage of XP users can patch their machines

    4. Re:Site's not Firefox-compatible by Anonymous Coward · · Score: 0
      You're right! That's because nobody could figure out how to patch their machines int he first place!

      Er - have you used a mainstream linux desktop distro recently? It is like .... 'click on the update icon and wait'...

      Liar! It's much more complicated than that. It's 'click on the update menu item, type the root password, click install all, and wait'.

    5. Re:Site's not Firefox-compatible by Decaff · · Score: 1

      Liar! It's much more complicated than that. It's 'click on the update menu item, type the root password, click install all, and wait'.

      Hah! Got you there! Not if you are already root!

  13. Not 2pm ET, but 2pm PT by adagioforstrings · · Score: 1

    The security update will be available at 2:00 pm PT as MS06-001. In any case, I'm glad to see Microsoft listening to customers and security advocates to release before the regular monthly patch date.

    1. Re:Not 2pm ET, but 2pm PT by rapid_snail · · Score: 1

      It has been already released. Get it here(if you run Windows, that is) http://www.microsoft.com/technet/security/Bulletin /ms06-001.mspx

  14. Really? by Life700MB · · Score: 2, Interesting


    Is really a problem of customer sentiment, or is actually the public embarassment of a third party releasing a patch quicker even without the source code of the libraries?


    --
    Superb hosting 20GB Storage, 1_TB_ bandwidth, ssh, $7.95

    1. Re:Really? by EvanED · · Score: 1

      is actually the public embarassment of a third party releasing a patch quicker even without the source code of the libraries?

      If by "patch" you mean "untested workaround that disables other functionality" then you might have a point.

      The unofficial patch isn't really comparable.

  15. What the MS patch does by Anonymous Coward · · Score: 2, Funny

    Let me guess, they've added a warning message that says you're about to download or open a WMF then let's you do it anyway? It took them all week to develop because they needed to translate "OK" and "Cancel" to 47 different languages.

    1. Re:What the MS patch does by Tony+Hoyle · · Score: 1

      Nah the majority of the work was getting the animation sequences for clippy right.

    2. Re:What the MS patch does by heson · · Score: 1

      "It looks like you are trying to run a remote exploit..."

    3. Re:What the MS patch does by Tim+Browse · · Score: 1

      "It looks like you are trying to tell a 5-year old joke..."

  16. Fix? by snib · · Score: 0

    I wonder if this actually fixes the problem or protects against it like Windows OneCare does.

    --
    This message will self-destruct in 5, 4, 3...
  17. Thank you, Big Brother by Gadren · · Score: 5, Insightful

    "It appeared that there had even been demonstrations to thank Big Brother for raising the chocolate ration to twenty grammes a week. And only yesterday, he reflected, it had been announced that the ration was to be reduced to twenty grammes a week. "

  18. I call bullshit by Anonymous Coward · · Score: 2, Insightful

    Somebody within M$ finally awoke to the public outcry from the sysadmins and ISC. Leaving your customers swinging in the breeze for weeks to release such a critical patch is criminal.

    1. Re:I call bullshit by Anonymous Coward · · Score: 0

      Yes...rushing a patch out without testing it is much better.
      http://www.checksum.org/cso/message/13465.html

      -W

    2. Re:I call bullshit by Anonymous Coward · · Score: 0

      Sorry dude, you must have thought you were posting somewhere else..
      Even though you are pointing out something so obvious that if it occurred in the Linux world it would be shrugged off.

      I fully expect replies to your post to follow the lines of:
      "That's one person and it is circumstantial.. how do we know this isn't a microsoft collaborator trying to FUD this third party patch that makes them look bad?"

  19. Old Systems by Anonymous Coward · · Score: 0

    As far as I know, this vulnerability dates as far back to Windows 3.1. A large number of users still run Windows 95/98 who can't get the patch from Microsoft. I guess it sucks to be them...

    1. Re:Old Systems by VAXcat · · Score: 2, Insightful

      It they're still running Windows 95/98, it already sucked to be them...bug, patch, or no...

      --
      There is no God, and Dirac is his prophet.
    2. Re:Old Systems by baadger · · Score: 1

      You laugh but i recently dug up 14 floppies of the original Windows 95 release, thats pre-SP1 (which was only released months later). It totals 21mB's and i'm tempted to install it for fun.

      The IE5 SP2 package (weighing in at 84.4mB it was the version of IE before IE6) still gets Windows 95 users access to windows update I believe, just no water running in them pipes now.

    3. Re:Old Systems by rooster9 · · Score: 0

      Insightful? You're just a jackass. Please explain to me again why I should spend $99 to upgrade an old computer (running ME) that is only used to surf the internet occasionally? Thought so.

    4. Re:Old Systems by Anonymous Coward · · Score: 0

      Please explain to me again why I should spend $99 to upgrade an old computer (running ME) that is only used to surf the internet occasionally?

      Well, duh, to be able to surf securely. Ever heard the expression, "You gotta pay to play"?

      And if that's all you do with it... Install Linux, problem solved.

  20. Gates has egg on his face by digitaldc · · Score: 0, Redundant
    --
    He who knows best knows how little he knows. - Thomas Jefferson
  21. Not "will", "did" by torunforever · · Score: 1
    Microsoft has just announced that they did release a security update for the .WMF-exploit today at 2pm ET

    It's 4PM now, so I fixed that for you.

    1. Re:Not "will", "did" by Krach42 · · Score: 1

      You must be new here... The way Slashdot articles are posted, it could have been "will" when it was submitted, then turned to "did" in the meantime before it was posted.

      --

      I am unamerican, and proud of it!
    2. Re:Not "will", "did" by ptomblin · · Score: 1

      then turned to "did" in the meantime before it was posted

      then turned into "no longer" by the time Cmdr Taco posts a dupe.

      --
      The next Cmdr Taco duplicate will be ready soon, but subscribers can beat the rush and see it early!
    3. Re:Not "will", "did" by Anonymous Coward · · Score: 0

      It's not 2 in Pacific Time. RTFA.

  22. early my eye by sardiskan · · Score: 1

    It's the old "SCOTTIE" trick. They say they need until the 10th to test and patch and make sure it works and then they WOW us by being able to release it early. They had it ready before now, they are just trying to salvage what little they have out of this fiasco.

    1. Re:early my eye by Fhqwhgadss · · Score: 1

      No, no, no. It's all right, you see. They still need until the 10th to test and patch, it's just that they did the "patch" part first. Now it's up to you to do the "test" part.

      --
      How does a 7-person democracy cut a pie? Into 4 pieces.
    2. Re:early my eye by sardiskan · · Score: 1

      Only M$ can give it's customers the chance to test. WOW. I am so freakin impressed. I'm writing my check for vista right NOW!

    3. Re:early my eye by javaxman · · Score: 4, Interesting
      It's the old "SCOTTIE" trick. They say they need until the 10th to test and patch and make sure it works and then they WOW us by being able to release it early. They had it ready before now, they are just trying to salvage what little they have out of this fiasco.

      They had it ready, if by ready you mean a version had been compiled and 'tested' once on the developer's machine.

      Trust me, right now in Redmond there's a whole team of Quality Assurance Engineers who are looking at their test plans, scratching their heads, and once again calling into question the actual value of their work, given that some manager can arbitrarily decide when it's time to rush a release regardless of what the schedule said or what the impact of a patch was or which cases remain un-tested. That, and they're really, really tired after pulling a couple of all-nighters.

      Have fun testing that patch.

    4. Re:early my eye by Geoffreyerffoeg · · Score: 1

      Indeed.

      There's probably some dual-boot Win3.1 and Win95 OSR 2 machine on a 486 in Slovenian that isn't compatible with the patch because they used "Slovenian" on the Win95 boot sector and "Slovene" on the Win3.1 boot sector, and the 486 doesn't have the instructions needed to equate the two, and the software emulation of that feature was only implemented in Windows 98...so the patch won't install, because it can't detect the language for the installer...and since both 3.1 and 95 have WMF formats, both operating systems are vulnerable.

      And it's Microsoft's responsibility - since it's an official patch - to make sure it will work on that machine. If they installed Ilfak's patch and it said "WTF .NET!?" then they couldn't complain...but if Microsoft's patch did that, then they could very likely sue if their computer got infected.

      (Okay, this is hypothetical because they end-of-lifed Windows 3.1. But you get my point. MS is responsible for ensuring that no machine that can reach Windows Update will be exploited.)

    5. Re:early my eye by Clover_Kicker · · Score: 1

      > then they could very likely sue

      Which version of Windows (or any other shrink-wrapped software) allows you to sue the vendor?

      Yeah, that's what I thought.

    6. Re:early my eye by javaxman · · Score: 1
      Which version of Windows (or any other shrink-wrapped software) allows you to sue the vendor?

      That depends entirely on your jurisdiction... and your ability to fund a lawsuit against Microsoft, of course... but that license that says you can't sue the maker of that software no matter what ? It may not be binding where you live. IANAL, of course, but product liability laws aren't nullified because you placed a shrink-wrap license in with your product.

    7. Re:early my eye by Clover_Kicker · · Score: 1

      Has anyone sucessfully sued a software vendor for a defect in their product, in any jurisdiction?

    8. Re:early my eye by javaxman · · Score: 1
      Has anyone sucessfully sued a software vendor for a defect in their product, in any jurisdiction?

      It depends on your definition of "successful". In many cases where it really matters, the software vendor issues a patch and everyone is ( relatively ) happy. Lawsuits seem to happen a ( bit ) more often when there is a contract between two parties- not really your shrink-wrap software case. And, of course, in situations where the software is contained in a physical device, like a car or router or printer, there is usually a recall involved to fix the problem ( or there would be a lawsuit, to be sure ).

      However, there have been several lawsuits against companies for what amount to software issues ( sometimes even if they aren't bugs ) - for example, if you look at the wikipedia page on AOL you'll notice that they were sued ( and settled ) because of problems users had with the 5.0 client installation. So... if the vendor pays $15 million to settle a claim due to problems with their software, is that a 'successful' lawsuit? I'd tend to think so, even if it might not be legally a loss, strictly speaking.

      What is clear is that even with a strong EULA, software products are not immune to product liability lawsuits; you are still selling a product, and if it harms your customer or doesn't work as advertised, you are open to lawsuits just like any other manufacturer.

  23. Oops by adagioforstrings · · Score: 1

    Well, I guess it already is out. Guess they got their announcement mixed up.

  24. MS Security Bulletin Link by ecliptik · · Score: 1, Redundant

    Here's the actual link to MS's site that describes the patch: Microsoft Security Bulletin MS06-001

  25. MS Gets Up Early To Issue Patch! by Quiet_Desperation · · Score: 5, Funny
    "I usually sleep in to a reasonable hour for a Thursday, like, noon," said Microsoft, appearing at 8am at a press conference outside a Hardee's in Iowa, dressed in slippers and a blue bathrobe with the words 'Sexy Grandpa' emblazoned on the back. "But all you whiiiiiiiiners wouldn't let me get my rest. So I'll crank this thing out and have it on Windows Update by 11am."

    "When will the patch for the patch be released?" asked Fox News correspondent Bubbles McConnifer, causing the press corps to giggle like schoolgirls in heat.

    "Smile when you said that, bitch," growled a visibly angered Microsoft, who then motioned to two pinstripe suited thugs who escorted Ms. McConnifer from the press conference.

    "Any other questions, whores?" asked Microsoft, placing fists on hips and allowing his 'MS Certified Otakus Rule!' T-Shirt to be seen. His query was greeted by silence. "Well alright, then."

  26. Re:first post? by Anonymous Coward · · Score: 0

    I'm sorry man, maybe in another couple of years? :)

  27. How many uploaded the "hacked" version? by webword · · Score: 1

    I'd like to know how many people downloaded and installed the "hacked" version(s). Any firm numbers out there? Thousands, hundreds of thousands, millions?

    1. Re:How many uploaded the "hacked" version? by webword · · Score: 1

      Damn your eyes on that title!

      Downloaded, downloaded, downloaded.

    2. Re:How many uploaded the "hacked" version? by winkydink · · Score: 1

      Yesterday, somebody on a sysadmin list mentioned that at his ISP, they were seeing about 6 infected machines per day on /16. He didn't say how full the adrress space was, but even at 25% utilization, that's 6 out of 16k. Not exactly Melissa.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  28. Rough translation by ctid · · Score: 4, Funny
    testing has been completed earlier than anticipated

    Our customers are getting pwn3d.
    --
    Reality is defined by the maddest person in the room
    1. Re:Rough translation by sharkey · · Score: 2, Interesting

      Since when did that matter to Bill & Co.?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    2. Re:Rough translation by Anonymous Coward · · Score: 0

      The dumbos we expect to buy Vista are getting pwn3d.

  29. I know, I know... by Eberlin · · Score: 3, Insightful

    Damned if they send out patches as they're made (too many, too confusing) and damned if they wait 'til Patch Tuesday (negligent, inconsiderate).

    We can't have it both ways, and neither should they. I say send out patches as they're made and let the sysadmins be responsible for whether they can keep up or not. It may be difficult to admin many machines that have to be patched but I'd rather have fixes available ASAP and put the burden on IT to apply them.

    Yeah, there are patches that will break stuff and ample testing should be done anyway...but does rolling them all into a Patch Tuesday really change that fact? Probably not.

    With this sentiment, we can put more pressure on Patch Tuesday for what it really is -- a Trustworthy Computing PR stunt in which the number of fixes and vulnerabilities seems to be lower (since we're only patching once a month...maybe).

    All that said, kudos to MS for reacting...but unkudos for taking this long...and major unkudos for being naive about the WMF design to begin with.

    1. Re:I know, I know... by 99BottlesOfBeerInMyF · · Score: 1

      Damned if they send out patches as they're made (too many, too confusing) and damned if they wait 'til Patch Tuesday (negligent, inconsiderate).

      Yup, but not damned if they fix the obvious design blunders that lead to many of these exploits, do security audits before releasing new technologies, and build an architecture that is not so brittle so that users don't have to worry that a patch to the web browser will break both core OS functions and third party applications.

    2. Re:I know, I know... by jaseuk · · Score: 1

      Actually I don't think it's the corporates that are the issue. Anyone with a large network is using some sort of patch management tools such as WUS or some 3rd party tool, they get to release the patches as and when they wish after they've had the change to test properly.

      The real problem with dropping patches all the time is that regular home users will get really pissed off with windows update rebooting their machine several times a week, users pissed off with updates will switch off the updates and no one really wants that to happen.

      So the two week cycle is a careful balance between user annoyance vs speed of patching.

      Of course any really critical patches should be released as soon as they are ready, the non-critical could wait for the twice monthly slot.

      Jason.

  30. It still took a long time! by LinuxDon · · Score: 3, Interesting

    The exploit writers have had the exploit ready for quite a while now.
    While MS was 'testing' everyone has been installing 'fixes' from other sites..
    Even IF their patch was not 100% it wouldn't really have mattered in this case.

    There was a gaping security hole in their OS and they still needed 12 days to come up with a fix!
    For such a large company whose software is being used by *millions* of people worldwide and 7 billion a quarter profit, they've sure taken their sweet time!

    Why don't they take some 0.01 procent of that 7 billion and test/release it sooner?

    1. Re:It still took a long time! by BruceCage · · Score: 1

      I thought Microsoft's early "patch" was unregistering the DLL? If people did that wouldn't that have closed the gap?

      --
      Perfect is the enemy of done.
    2. Re:It still took a long time! by skiman1979 · · Score: 1
      unregistering the DLL
      well that and changing the name of the DLL to something else so other applications can't reregister it.
      --
      Having a smoking section in a public restaurant is like having a peeing section in a public swimming pool.
    3. Re:It still took a long time! by Keeper · · Score: 1

      If an exploit is re-registering it, your box is already 0wn3d.

    4. Re:It still took a long time! by skiman1979 · · Score: 1

      I realize that, but if a ligitimate application is being installed, and that application uses the aformentioned dll, it will register it, will it not?

      --
      Having a smoking section in a public restaurant is like having a peeing section in a public swimming pool.
    5. Re:It still took a long time! by Keeper · · Score: 1

      No, it won't. This isn't an application redistributable. No application installs it, and no application registers it. It is installed and registered with the OS.

    6. Re:It still took a long time! by Zathrus · · Score: 1

      There was a gaping security hole in their OS and they still needed 12 days to come up with a fix!

      Because, you know, if you impregnate 9 women you get a baby in 1 month!

      Come on folks. While I think MS dragged their feet on this one, and the "feature" was insanely stupid in the first place, we're still talking about software development here. Throwing resources at a problem does not necessarily help.

    7. Re:It still took a long time! by obeythefist · · Score: 1

      12 days is very, very fast.

      Think of the sheer level of complexity that Windows code is (some mangled mess of DLL's and API's all shunting through a small 16bit module that says (c)1984 Bill Gates on it)

      It would take a very awesome effort to make sure that a low level patch like this doesn't mess up with any of that code. Or any code made by any of *hundreds* of "partners". That is not an amount of testing anybody can honestly hope to complete within an hour.

      Microsoft can't afford any more bad PR on windows updates breaking things. They got enough (unfair) PR because they enabled the firewall in SP2 by default (something the /. community was constantly complaining wasn't done, and when it was they complained about that, too).

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
  31. Error in the summary... by Ransak · · Score: 3, Funny
    The security update will be available at 2:00 pm PT as MS06-001.

    ... meaning all us east coast admins will be staying late tonight. Joy.

    --
    "Powers. I have them."
  32. Way too late. by Ymk · · Score: 1

    I had this virus on my desktop spamming it's false alerts since as early as last week. After I fonud the proper guides on how to remove it, and an arguous 5 hour sessions of reboots, safe mode runs, virus scans from 5 different programs, and constant tweaking and adjusting, I finally removed the virus on my own. Thanks Microsoft...

  33. Clip Art by scolby · · Score: 2, Interesting

    Intrigued with the broo-haha surrounding WMFs, I did a search for them on my machine. The only WMFs I found were Microsoft's clip art. Which begs the question: is there anyone out there who isn't Microsoft who commonly uses this file type?

    1. Re:Clip Art by Anonymous Coward · · Score: 0

      It doesn't really matter because you can hide them inside .jpg's and other images

    2. Re:Clip Art by FhnuZoag · · Score: 1

      Sure. Before SVG, WMFs and EMFs were the only 'standard' vector image formats. Often, if you were working with AutoCAD etc, you would export to WMF or EMF to ensure that someone on the receiving end can see stuff and rescale correctly.

    3. Re:Clip Art by Anonymous Coward · · Score: 0

      Doesn't sound at all like it begs the question -- sounds like it prompts the question. Perhaps you didn't understand the language you were using, and only inadvertently came out sounding so foolish...

    4. Re:Clip Art by petermgreen · · Score: 1

      well its the standard windows vector format and as such is used for moving vector images between apps on the windows clipboard.

      also used in the windows printing system.

      as a file format its mainly used by clipart collections afaict. wmf is a pretty basic format (emf is somewhat better though) but its well supported and adequate for the purpose of clipart.

      its not as well known as bmp because there was no editor app supplied with windows and most pro stuff encouraged use of its native format.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    5. Re:Clip Art by Just+Another+Poster · · Score: 1

      It looks like the format isn't so obsolete after all. Office XP's Media Content CD contains around 20,000 WMF images, dated from 1998 through 2000.

  34. New Microsoft Acquisition by Ctawp · · Score: 1

    In other news, Microsoft bought out the company that originally patched the flaw. ;)

    1. Re:New Microsoft Acquisition by Skiron · · Score: 1

      Bill Gates would never sell...

  35. MOD PARENT TROLL by Anonymous Coward · · Score: 0

    To parent: If you were in change of Microsoft's update team, would you spend your time developing an update system for various other companies products if you had one you knew would work 100% of the time for the required task?

    I'm no anti-microsoft zealot as I enjoy using other products, but the groupthink on this website is rediculous.

  36. Early release to catch out the hackers by briqui · · Score: 3, Insightful

    Telling everyone that they are going to wait till Tuesday to patch the problem, then releasing a patch 5 days earlier might actually be quite a neat trick.

    I'm sure a lot of people out there who were planning to taking advantage of this problem have been thinking that they have till Tuesday to write a really good exploit, and therefore not hurrying too much.

    Now Microsoft come along and patch it early.

    I don't know about anyone else but I was expecting Monday do be a day from hell...

    1. Re:Early release to catch out the hackers by bogie · · Score: 2, Interesting

      "I'm sure a lot of people out there who were planning to taking advantage of this problem have been thinking that they have till Tuesday to write a really good exploit, and therefore not hurrying too much."

      I don't believe that for a second. People who wanted to take advantage of this flaw had their code done with 48hrs of the public disclosure. No serious hackers we waiting till this weekend to try and catch some people. It's a race you see. The last thing they wanted was to wait a week and let Antivirus makers and consumers get wise to this and start taking precautions.

      IMHO MS releasing this early is due to bad PR and massive pressure from customers. I think it had nothing to do with "tricking" crackers.

      And I also want to say thanks to a "real" hacker. Running around like crazy to install that 3rd party patch probably saved me from mucho headaches. Jeers to MS to taking so freaking long.

      --
      If you wanna get rich, you know that payback is a bitch
  37. Right... by Anonymous Coward · · Score: 2, Funny

    Does this mean I can't have an image file that creates bouncing pictures hopping around on my screen with some guy screaming that I am looking at gay porno?

    srsly, fuck u miKKKro$haft

  38. The Real Reason by guaigean · · Score: 2, Insightful

    Actually they are doing this to save face. The reason it is being put out "early" is because someone else wrote a fix for it already. People apparently flowed to this other site for the patch, and people started wondering what the problem was. Here was a person who without the Windows source fixed the bug, while Microsoft itself with full access to the code was delaying. In order to save face they had to rapidly deploy it rather than sit on it as they normally do.

    --
    Microsoft Sucks, F/OSS Rocks. I get mod points now right?
    1. Re:The Real Reason by TubeSteak · · Score: 3, Informative

      The other guy didn't fix the bug.

      he did not fix it

      All the 3rd party patch did was implement a workaround.

      --
      [Fuck Beta]
      o0t!
    2. Re:The Real Reason by Scarblac · · Score: 1

      The other guy didn't fix the bug. he did not fix it All the 3rd party patch did was implement a workaround.

      The thing is, this vulnerability isn't a bug. WMF files have a feature that allows them to register a callback function, and that callback function can do whatever it wants. Someone apparently thought it was a good idea at the time...

      The 3rd party patch disables that feature. As does Microsoft's patch. You might call it a workaround, but what else is there to do?

      --
      I believe posters are recognized by their sig. So I made one.
    3. Re:The Real Reason by TubeSteak · · Score: 2, Funny

      this vulnerability isn't a bug

      lol, it's a feature.

      these jokes write themselves.

      --
      [Fuck Beta]
      o0t!
    4. Re:The Real Reason by Anonymous Coward · · Score: 0

      All the 3rd party patch did was implement a workaround.

      Which turns out to be the same workaround that Microsoft implemented trying to save face. As usual M$ waits for someone else to come up with the idea first then borrows it for their own sorry implementation.

    5. Re:The Real Reason by Anonymous Coward · · Score: 0

      Learn to spell, asshole. Fact is, in this case the vulnerability was not the caused by a bug per se but rather by a badly designed system. Of course you could just as well call the whole system a bug, but that is a matter of semantics which I am not interested in.

  39. 2000, XP, 2003, but no 3.10, 3.11, 95, 98, or ME? by mosel-saar-ruwer · · Score: 2, Informative

    I'm only getting hits on 2000, XP, and 2003:
    http://www.microsoft.com/downloads/results.aspx?fr eetext=KB912919
    According to the Financial Times article highlighted at Drudge, Hyppönen said the vulnerability is supposed to hit "every Windows operating system since 1990".

    So is there a patch for older versions of Windows?

  40. Sober is the reason IMHO by PaxTech · · Score: 2, Interesting
    There's speculation that when sober.z goes into action tomorrow it may try to download a WMF exploit, hence the quick turnaround on the patch.

    I think that by this point Microsoft is pretty much numbed when it comes to public embarrassment.

    --
    All movements for social change begin as missions, evolve into businesses, and end up as rackets.
  41. Does *not* require Internet Explorer... by SenorCitizen · · Score: 4, Informative
    Thank you for your interest in obtaining updates from our site. To use this site, you must be running Microsoft Internet Explorer 5 or later.

    Funny, yes, but not true. The patch is available here:

    http://www.microsoft.com/technet/security/Bulletin /MS06-001.mspx

    Just downloaded it with Firefox. It's just Windows Update that requires IE.

    1. Re:Does *not* require Internet Explorer... by Blakey+Rat · · Score: 1

      Technically, that's a different "site" and the message is correct. But, yeah, it would be nice if it just fed you a link to the non-Windows Update download site if you try to use Windows Update with Firefox or whatever.

    2. Re:Does *not* require Internet Explorer... by Heraclius · · Score: 1

      Just downloaded it -- what fascinates me is that both on that page, and when you go in through Windows Update, the description of the problem doesn't say the magic string "WMF" anywhere, until you drill down several pages to get details. So even if people are looking for the fix to the "WMF" problem it's not going to be obvious to them whether it's there or not.

    3. Re:Does *not* require Internet Explorer... by techfury90 · · Score: 1

      It's not really a WMF specific exploit, all a WMF is is a file of GDI calls basically. The exploit can be done in a WMF because they allow you to contain GDI calls, and the hole was in GDI.

      --
      I'm friends with the youngest daughter of the former head of the PowerPC division of IBM you insensitive clod!
  42. 3rd party did not patch vulnerability by badriram · · Score: 3, Insightful

    They just blocked the execution of the vulnerable function. This to me a mitigation method not a patch. Think of it as, there is a vulnerability in mod_rewrite within apache, and a third party "patch", just disables it, to secure apache.

    1. Re:3rd party did not patch vulnerability by superdoo · · Score: 1

      But apparently Microsoft's patch does the same thing. From their FAQ:

      Does this update contain any security-related changes to functionality?
      Yes. The change introduced to address this vulnerability removes the support for the SETABORTPROC record type from the META_ESCAPE record in a WMF image. This update does not remove support for ABORTPROC functions registered by application SetAbortProc() API calls.

    2. Re:3rd party did not patch vulnerability by Anonymous Coward · · Score: 0

      No. Microsoft's solution invalidates the picture file's ability to define it's own abort procedure by using the SETABORTPROC flag. This method is done in the core of GDI itself and does not impact any running programs. Programs may still use SetAbortProc() to define their own abort procedure.

      The third party solution was a hack. It used a hook to force a process injection so that the fix code would be interjected into the memory space of all executing processes. The interjected code would then attempt to override the import table of functions of the process in order to install a proxy for the GDI Escape method. That proxy would intercept calls to the method and if the call attempted to set an abort procedure it would not forward the call to the proper GDI Escape method, regardless of where the request originated.

      This hack involved forcing third-party code into the process space of all processes and interfering with the import table. The extra code would increase the memory usage of all applications and incur a performance penalty to any application calling the GDI Escape method regardless of reason. Also, there are built in countermeasures in Windows to cause systemwide hooks to get shutdown under certain scenarios, such as when the user hits Ctrl-Alt-Del, and processes launched after that point would no longer have any protection.

      Lastly, only one of these methods endured any serious testing. Anyone could toss together this hack in about an hour. I've done this very thing myself in order to proxy Send/PostMessage to prevent shatter attacks, as well as to intercept keyboard messages caught in a hardware accelerated environment. Granted this kind of stuff works, but interfering with the process space of other programs may compromise the integrity of those programs and cause stability issues. I'd rather take the official, tried and tested fix.

  43. Fixes already in the wild though? by shoptroll · · Score: 2, Informative

    This wouldn't have anything to do with the fact that the fix got leaked early, would it?

    http://grc.com/sn/notes-020.htm

    --
    Insert Sig Here
    1. Re:Fixes already in the wild though? by shoptroll · · Score: 1

      In addition, someone else already released a temp fix, according to the link.

      Should've hit preview before submitting again.

      --
      Insert Sig Here
  44. One Size Does Not Fit All by EXTomar · · Score: 1

    The problem MS has with their patching strategy is that problems are not one size fits all. There are things in various parts of Windows and other MS products that are low priority to update and will not be happy if I have to push out something out of cycle. On the other hand, there are very serious critical flaws that are very high priority that I would like to have immediately and would push out to every machine I could find immediately.

    All problems are not the same quality or severity so why is MS trying to treat them as such?

  45. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by MightyMartian · · Score: 2, Funny

    Boy, all those guys running web servers under DOS 5 must be pissing their pants!

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  46. Why not... by darthservo · · Score: 2, Funny

    Use the exploit to their advantage? Just change their logo to a WMF and use the exploit to push the patch out?

    --

    Prove it.

  47. that's the funniest, cleverest, bestest comment by Anonymous Coward · · Score: 0

    ever. Or maybe I've just had too much diet coke.

  48. Anyone else a bit... sad? by Tomji · · Score: 1

    Somehow I would have liked this to not come out until then, esp. since so many companies refused to install anything non-MS.
    I did install the patch on my networks, and now I feel like my time was wasted and the stubborn people won.

    I guess next time I go with the lazy people.

  49. Sadly no by badriram · · Score: 2, Informative

    Here is the FAQ from the KB
    -----
    Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) were previously listed as affected, but are no longer listed. Why is that?
    Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, at this point in the investigation, an exploitable attack vector has not been identified that would yield a Critical severity rating for these versions. Per the support life cycle of these versions, only vulnerabilities of Critical severity would receive security updates. For more information about the security update support policy for these versions of Windows, visit the following Web site.
    -----

    Although I do believe they should be patching this.

    1. Re:Sadly no by Tony+Hoyle · · Score: 1

      So what about NT4?

      There are a *lot* of companies still using that on the backend servers and on the desktop (not sure if it's still the majority but it's very significant).

    2. Re:Sadly no by diersing · · Score: 2, Insightful
      There are a *lot* of companies apparently with their collective heads up their asses.

      If you are in this predicament, of supporting an NT4 environment - I feel for you, I really do. Seriously at some point avoiding the costs of upgrades is going hurt more then cutting the dang check.

      ask not for whom the bell tolls...

    3. Re:Sadly no by Tony+Hoyle · · Score: 3, Insightful

      No, they're just companies that can't spend half a million dollars upgrading hardware and software just to run the latest whizz-bang eye candy from microsoft, when what they have works just fine.

      Over 40% of our customers are NT4 shops. Some of them are *big*.

    4. Re:Sadly no by Derek+Pomery · · Score: 1

      The only reason there is no attack vector is because no one has bothered
      to write an exploit yet. As soon as the others get patched, that should
      happen soon enough. Based on the description of how this exploit works,
      Microsoft's attitude toward's Billy G's "My First OS" is baffling.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    5. Re:Sadly no by c0d3h4x0r · · Score: 1

      when what they have works just fine.

      Yeah, it obviously works just fine, given that there's a huge security flaw in it.

      --
      Moderator hint: a comment is neither "Flamebait" nor "Troll" if it is true.
    6. Re:Sadly no by Pii · · Score: 3, Informative
      Actually, the reason there's no attack vector is because while the same vulnerability on older versions of Windows, older versions of Windows don't have the Microsoft Picture and Fax Viewer configured as the default file handler for .wmf files.

      Ironic, as the older operating systems come from a time when that format may have been relevant. It's kind of funny that only after the Windows Metafile became obsolete did MS choose to create a default program association.

      --
      For those that would die defending it, Freedom
      has a sweet taste that the protected will never know.
    7. Re:Sadly no by jazman_777 · · Score: 1
      ...when what they have works just fine.

      This is Slashdot. Please mod parent "funny".

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    8. Re:Sadly no by skwirlmaster · · Score: 1

      Honestly I hope they aren't:
      1) Running IM software
      2) Checking e-mail
      3) Surfing the web...

      on their backend machines.

      This exploit works by opening/viewing a WMF file, which is an image file. I know there are legit reasons to have WMFs on a NT Server. However, you probably shouldn't be downloading new ones randomly off the web. If these machines are some sort of net storage, you probably would use another machine to make use of these files. The only real threat your backend should have is a worm payload deposited on an infected 2k/XP/2k3 machine.

      --
      My inner self is ineffable, so don't eff with me.
    9. Re:Sadly no by Sarisar · · Score: 1

      They say it isn't critical in the systems they are not patching! How much bullshit is that? If it is the same problem in all systems (and other people have said it was) then how can it be critical in some but not others?

    10. Re:Sadly no by Derek+Pomery · · Score: 1

      I fail to see how that helps.
      F-secure stated that MS Paint could be vulnerable as well, and others.
      And given the nature of the exploit, it seems almost anything that reads a WMF could be a vector.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    11. Re:Sadly no by Bert64 · · Score: 1

      It's funny how something which is touted as being so good 8 years ago, is now advertised as not being up to the task simply because they have something new to sell...
      Anything it could do 8 years ago, it can still do now... Most organisations are still doing the same things now that they were 8 years ago, so why bother changing?

      On the other hand, people could argue that NT4 was never really up to the task and all the marketting was just lies, but the same could also be said about current versions.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    12. Re:Sadly no by deaddrunk · · Score: 1

      It doesn't work just fine, it has a huge honking great security hole in it.

      --
      Does a Christian soccer team even need a goalkeeper?
    13. Re:Sadly no by diersing · · Score: 1
      The fact that they are *big* certainly factors in since upgrading would be a *big* project. But in my experience with big companies, the deployment projects always include 5 & 10 year hardware/software upgrade costs (as they should).

      Hardware costs aside my guess is these server runs a specific function the enterprise needs?, is there an open source alternative that could utilize the existing hardware but provide a current platform that will be supported going forward? NT4 support is dwindling and in my experience, security folks are enforcing its removal because over security concerns that challenge availability, integrity and confidentiality to critical data.

  50. will? or did.. by mottie · · Score: 3, Interesting

    Posted by CmdrTaco on Thursday January 05, @12:56PM (3:56PM EST)

    Chran writes "Microsoft has just announced that they will release a security update for the .WMF-exploit today at 2pm EST


    talk about releasing the news late.. the patch was already out by the time slashdot had the "news" that microsoft would be releasing the patch.

  51. MS innovation by Skiron · · Score: 1

    Obviously they looked at how he fixed it, snarfed it, and now we will see how 'MS innovation' spin produces a hotfix in record time.

  52. Not that by SuperKendall · · Score: 1

    They would have released it earlier, but their test machines kept getting hacked...

    I heard it was because they were having a tough time to come up with the $40 a computer needed to aquire the software to distribute in the patch.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  53. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by Anonymous Coward · · Score: 0

    I vote this the most misinformed message of the day! (re the WMFs)

  54. And now for the "for Nerds" part of the article by MagicM · · Score: 1
    From the bulletin:
    The change introduced to address this vulnerability removes the support for the SETABORTPROC record type from the META_ESCAPE record in a WMF image.

    So all of you out there with WMFs with SETABORTPROCs in your META_ESCAPE records, beware!
    (Not sure what I just said.)
  55. Who gets up early? by mmell · · Score: 2, Funny
    At a recent Comdex event, Bill Gates announced to the world "I am Microsoft!"

    His wife could not be reached to comment on this!

    ***rimshot***

    Thanks folks! I'll be here all week. Don't forget to tip the wait staff.

  56. "testing ... completed earlier than anticipated" by antispam_ben · · Score: 4, Insightful

    Translation: "Our ass needed covering even earlier than anticipated."

    --
    Tag lost or not installed.
  57. 1st Party did not patch vulnerability either, then by algae · · Score: 2, Informative

    By your logic, Microsoft also has not patched the vulnerability. From the MS006-001 FAQ:

    Does this update contain any security-related changes to functionality? Yes. The change introduced to address this vulnerability removes the support for the SETABORTPROC record type from the META_ESCAPE record in a WMF image. This update does not remove support for ABORTPROC functions registered by application SetAbortProc() API calls.

    So, they basically used exactly the same workaround as the 3rd party patch that's been out for a week.

    --
    Causation can cause correlation
  58. Case Studdies by PacketScan · · Score: 1

    Great you have done a Case study on me..

    SO Now EVERYONE know what i'm running and what i may or may not be Vulnerable to.

    I wouldn't doubt that Xerox and rest called MS and Blew their top.

    Not to mention you can just goto http://www.microsoft.com/resources/casestudies/ for a list of targets

    We are a smaller shop we have about 100 desktop/servers. I called and voice my oponion in a calm and Firm fashion. I guess ALOT of others did as well.

  59. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by theguyfromsaturn · · Score: 1

    I'm conviced that it should hit every version of Windows. I have been embedding wfm for my thesis and proposals win 1998. I had lots of memory problems using either Word or Word Perfect to open those documents. Even with only a few wmfs embedded in Excel, or other third party applications (that were obviously using windows API to render them). Then I switched to StarOffice and the problem vanished... for me. My supervisor, with a much more powerful computer still had trouble. I guessed at the time that it was some kind of memory leak in the Windows rendering engine, and since StarOffice was cross-platform, they were probably using their own code to render it, and not the API. Back then I only thought how nice it was to be using StarOffice instead of constantly rebooting the computer and getting nothing done. I never thought back then that memory leak could mean buffer overflow which could mean security vulnerability. I have the feeling that it's related. Of course I'm not a computer guy. Obviously the bugs were never fixed from version to version, and I can't believe I'm the only one who noticed that wmf files, which are not supposed to take that much memory compared to raster images could turn into such a nightmare. My supervisor's Word still renders horribly wmf files that show very nicely in OpenOffice. To this day I still include my graphs as raster images for his sake.

    --
    I like my dinosaurs feathery, and my pterosaurs hairy (or is it pycnofibery?)
  60. Actually, MS posted the patch to shut ya' all up. by bob2cam · · Score: 1

    The real reason MS posted the patch is shut ya' all up and stop the blogsteria from continually feeding the tech media frenzy. My place of employment (30,000 users) has not had any problems with exploit, At my daughters place of employment (180,000 users all over the world) IT reports no problems with the exploit.

    But I want to thank you all for wonderful week of waiting for the sky to fall!

  61. MS: "vulnerability is not critical" by rbochan · · Score: 1

    "Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
    No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical because an exploitable attack vector has not been identified that would yield a Critical severity rating for these versions."
    from
    http://www.microsoft.com/technet/security/Bulletin /MS06-001.mspx

    Oooooooh boy, I feel for those folks that have older machines... they're basically fucked. MS doesn't even call this "critical".

    --
    ...Rob
    The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
    1. Re:MS: "vulnerability is not critical" by Anonymous Coward · · Score: 0

      For all the people knocking ME, I personally think it is a better choice than XP.

      I don't think many have actually used it, just heard prejudice about problems that idiots have.

      Anyway,

      the fuckers at microsoft, are idiots. They are blindly following some stupid rule ("well, duh, if there's no vectors yet, it's not critical, hyup"). Hopefully they'll patch it by next Tuesday at their scheduled time.

      The patches for XP (which will be ignored on about 80% of machines) will hopefully put a small dent in the spread of viruses, but there's still the problem of malicious websites and emails.

      Fuck i hate microsoft spokespeople.

  62. Early? by BumpyCarrot · · Score: 2, Insightful

    Early would have been before the original flawed release, surely?

    --
    Do you see what I did there?
  63. And finally... by imipak · · Score: 1
    I was intending to submit this as a story, but I'm sure someone else will save me the trouble in a few days' time ;)

    The - final? - twist in the long, strange trip of the WMF bug - the vulnerability that just keeps on giving - has been revealed by H D Moore, the author of the Metasploit exploits (which is now on a third generation and even tricksier than ever!:)

    After all the jokes about WINE compatibility... it turns out that WINE is vulnerable, too!!

    To quote the words of a song by H D's namesake, Dudley:

    Laugh? We nearly shat
    We had not laughed so much since Grandma died
    Or Aunty Mabel caught her left tit in the mangle...

    (And I'm posting from a Thinkpad running Mandriva GNU/Linux, the first time I've been 100% Billy free at work as well as at home since 2000, so I'm allowed to laugh... no WINE for me cos I only run Free software *smug* :)

    1. Re:And finally... by Slashcrap · · Score: 1

      After all the jokes about WINE compatibility [google.co.uk]... it turns out that WINE is vulnerable, too!!

      But to be fair, that's not what I would call a security hole in WINE. It's not a buffer overflow or any other kind of programming error on the WINE side is it? It's just that they copied incredibly insecure functionality from Microsoft.

    2. Re:And finally... by Anonymous Coward · · Score: 0

      Now on ZDNet as well:

      http://blogs.zdnet.com/Ou/?p=146

  64. Early? by Anonymous Coward · · Score: 0

    "Early"? It's too late to be "early".

  65. Win 98, Win 98 SE, Win 89 ME by IEBEYEBALL · · Score: 2

    Where are the patches for Win 98, Win 98 SE, and Win 98 ME? Microsoft rates this as a critical exploit and is supposed to release patches for critical exploits so where are they? Millions of people still use these operating systems.

    --
    -- SKYKING, SKYKING, DO NOT ANSWER.
    1. Re:Win 98, Win 98 SE, Win 89 ME by Anonymous Coward · · Score: 0

      Here is a patch for Win9x - made by an Italian guy who works for a company that produces the NOD32 antivirus product. It's about a 940kb download.
      http://www.nod32.ch/en/download/tools.php

    2. Re:Win 98, Win 98 SE, Win 89 ME by Toveling · · Score: 1

      They are out of their support lifes. They aren't supposed to get updates.

    3. Re:Win 98, Win 98 SE, Win 89 ME by IEBEYEBALL · · Score: 1

      Yes, but Microsoft certainly knows that perhaps millions of people still use 98, SE, and ME. Microsoft sucks for not putting out a patch for these OS's.

      --
      -- SKYKING, SKYKING, DO NOT ANSWER.
    4. Re:Win 98, Win 98 SE, Win 89 ME by Anonymous Coward · · Score: 0

      If Microsoft does not patch 98, SE and ME, then those users are all but forced to upgrade to XP if they want to use them on the internet. All those millions of upgrades means more billions for Microsoft. So where is the incentive for Microsoft to patch them?

    5. Re:Win 98, Win 98 SE, Win 89 ME by msobkow · · Score: 1

      "Millions?"

      You mean you couldn't be bothered updating. The only place I've seen seen anything older than NT 3 in the past 10 years was on a dust-gathering basement clunker that we booted for giggles. As many places will sell used machines with a newer version of Windows installed for Upgrade or get off the 'net. Your "beater" is a road hazard.

      --
      I do not fail; I succeed at finding out what does not work.
    6. Re:Win 98, Win 98 SE, Win 89 ME by Reziac · · Score: 1

      I ran the test util (linked from somewhere on GRC, I think) on my Win98 box, and it said "not vulnerable", I vaguely suspect thanks to something CorelDraw updated.

      Does anyone (er, anyone known to be trustworthy) have a benign proof of concept .WMF that could be used as a more direct test?

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    7. Re:Win 98, Win 98 SE, Win 89 ME by IEBEYEBALL · · Score: 1

      how about customer goodwill?

      --
      -- SKYKING, SKYKING, DO NOT ANSWER.
  66. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by Mercano · · Score: 3, Informative

    I never thought back then that memory leak could mean buffer overflow which could mean security vulnerability

    In this case, its not a buffer overflow bug. In fact, its not even a bug, per say. Its a feature, or at least a really bad design flaw that no one has stumbled upon/abused up until now. See F-Secure's writeup.

    --
    #include <signature.h>
  67. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by charlesnw · · Score: 1

    Believe it or not Dos is still run in production. I know. I have dos machines on my network.

    --
    Charles Wyble System Engineer
  68. Great.. yet another late night for sysadmins by nurb432 · · Score: 1

    Patching a few hundred servers is not how i wanted to spend my evening.

    --
    ---- Booth was a patriot ----
  69. Why at that time? by houghi · · Score: 1

    I would rather have them release it as soon as it is ready. Even if it is done in steps.
    Step 1) Release a fix that will close the security leak 100%, even if it means some things will not work anymore
    Step 2) get a relase that fixes everything so everything works as it should.

    Step 1 can be done in hours. Step 2 then has much less presure. It can be released when ready.

    I can't understand how you can put a date and even less a time on a security patch. What if they are ready earlier? What if they are not ready at all?

    --
    Don't fight for your country, if your country does not fight for you.
  70. The real reason it took 8 days by fastgood · · Score: 1
    According to MS06-001, you choose from one of 6 fixes for your particular flavor of Windows.

    I'd bet that 2000 SP4, XP Professional, and 2003 Server hardly took any time at all to prepare.
    The x-64 2003 server and x-64 XP PRO probably required a bit more preparation and testing.

    But someone in our party just had to order the 2003 Itanium-based product and make us all wait!

  71. Ilfak's unofficial patch did not require a re-boot by Futurepower(R) · · Score: 1

    Ilfak's unofficial patch did not require a re-boot. Microsoft's does. Supposedly both patches do exactly the same thing.

  72. Re:Seems to be available on Windows Update now by Anonymous Coward · · Score: 0

    I keep clicking there but nothing happens.

  73. Early? by mapmaker · · Score: 1

    Unless they're including a time machine in the patch, I would call this release "late".

  74. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by jschottm · · Score: 4, Informative

    Microsoft's policy is that they will only release critical patches for 9X/ME systems because they have EOLed them. Their study of the vulnerability found that while those systems are vulnerable, that it is not critical because no attack vector has been identified. Whether or not you trust their assessment is another question, but that's why there's no patch for them. See questions 2, 3, and 4 in the FAQ.

    http://www.microsoft.com/technet/security/Bulletin /MS06-001.mspx

    I suspect 3.x is the same, but really, if you're using 3.10 as a desktop...

  75. Re:Ilfak's unofficial patch did not require a re-b by MntlChaos · · Score: 2, Informative

    Ilfak's patch required a reboot to start applying to new processes, rtffaq.

  76. Standalone? Help? by Mike+Savior · · Score: 1

    I couldn't seem to find it.. is Microsoft doing a standalone distributable update (like for the flaw that took out some news networks) for large amounts of computers? A link would be helpful if someone had it.

    --
    space is pretty cool.
  77. "Early" was LAST WEEK by Philip+K+Dickhead · · Score: 2, Insightful

    This is "Less late".

    --
    "Speaking the Truth in times of universal deceit is a revolutionary act." -- George Orwell
  78. In other news today by Kesch · · Score: 1

    As an update to the story, Microsoft has announced that the patch release was a hoax.

    Hackers were supposedly able to infiltrate Microsoft systems after Bill Gates viewed an email in Outlook containing a WMF file diguised as a GIF. Other reports say Gates visited a site containing the compromised file while using IE.

    Bill Gates had this to say: "That's a lie. Everyone knows that I'm too smart to use IE or Outlook. Do I look like a retard to you?"

    Microsoft claimed that they had no intention of releasing a patch early, especially a working one.

    From the press release:

    We at Microsoft have specific guidelines to prevent this sort of thing from happening. A Windows platform that works perfectly would damage the booming IT industry. Microsoft is dedicated to providing a safe haven for up and coming sys admins and tech support specialists

    When asked about their aborted plans for the security fix, the PR spokesman replied, "This vulnerability has been fixed in Vista. Had the hackers not maliciously spread this patch, users could have oficially fixed it by shelling out $1,000 for Vista when it is released."

    In a final press release of the day, Microsoft has discovered a new vulnerability:

    It has been discovered by a team of experts at Microsoft that all Windows machines will explode violently the day after Vista is released. This problem does not exist in Vista, however. Becuase no known exploits exist for the vulnerability, the status is set at Super-Cute-Pink-Bunny-Harmless. Since it has such a low status, a patch should not be expected until a month after Vista has been released.

    --
    If this signature is witty enough, maybe somebody will like me.
  79. Nothing for 98 or ME? by Anonymous Coward · · Score: 0

    Apparently there's nothing for 98 or ME users...

    1. Re:Nothing for 98 or ME? by lucm · · Score: 1

      Yeah, there is no way to "exploit" anything on those versions...

      --
      lucm, indeed.
    2. Re:Nothing for 98 or ME? by Kesch · · Score: 1

      There are people who use ME that care about their OS enough to patch it?

      There are people who use ME that care about their OS?

      There are people who use ME?

      I'm confused.

      --
      If this signature is witty enough, maybe somebody will like me.
  80. Windows is patched, by Wine is exploitable. by Anonymous Coward · · Score: 1, Informative

    Anyone who uses Cross-Over Office, Cedega, or plain old Wine (all 10 of you) -- your system is vulnerable to the recent WMF exploit. Loading an office document in Cross-Over that has an embedded WMF file will execute arbitrary code on your system. Gamers -- any games that display user-defined graphics (avatars, etc) and accept the WMF/EMF formats, could be exploitable. A patch was submitted to the Wine development team, but it may not be available for a while (especially if you use a commercial derivative). Please see the following URL for more information:
    http://archives.neohapsis.com/archives/fulldisclos ure/2006-01/0173.html

  81. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by MightyMartian · · Score: 1

    Actually, we still have a number of old legacy apps for some specialized hardware that we're still using DOS software for. Fortunately, all but one will run in a DOS session under Windows. I actually still see quite a lot of DOS software out there, particularly with Point of Sale systems and the like.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  82. Somewhere ... by Kaelthun · · Score: 1

    ... and somewhere in the middle of all this speculation and interesting dabbling, a Microsoft intern is quietly stressed out because the patch he was preparing will never be beta-tested due to the management shifting the releasedate back ...

    --
    -------
    Userfriendly? Sure it is, unless you aren't computerfriendly!
    /me to a classmate on FreeBSD
  83. NO! by baadger · · Score: 5, Informative

    So, they basically used exactly the same workaround as the 3rd party patch that's been out for a week.

    The MS patch removes the call in the WMF rendering engine that calls the gdi32 Escape() function with the SETABORTPROC parameter. The 3rd party runtime patch thats been around 'for a week' killed the Escape() function's ability to receive the SETABORTPROC procedure in _all user32.dll bound applications_ called by _anything_ for _any purpose_, 'breaking' more than just the WMF rendering caller.

    Microsoft couldn't have done any better because this wasn't a coding error like a buffer overflow, it was an ancient long forgotten genuine feature.

    1. Re:NO! by Flammon · · Score: 1

      Ya ya, we know, it'a feature not a bug. Who do you report to at Microsoft anyway?

    2. Re:NO! by baadger · · Score: 2, Funny

      If i tell you he or she might throw a chair at me and/or fucking kill me

  84. GRC with Ilfak Guilfanov making patch for Win9x by Anonymous Coward · · Score: 1, Informative

    "If Microsoft Doesn't Fix Windows 98/ME, GRC will. Microsoft has "reclassified" the WMF vulnerability in Windows 95, 98, and ME as non-critical. This means that it will probably NOT be updated and patched for the WMF handling vulnerability that those older versions of Windows apparently have."

    So, if Microsoft does not produce an update to repair those older versions of Windows, GRC (Steve Gibson) will make one available.

    Source: http://www.grc.com/sn/notes-020.htm

    - I just think that maybe in near future patches for Windows from outside Microsoft will became more common...

    -xet7

  85. Re:1st Party did not patch vulnerability either, t by CFrankBernard · · Score: 1
  86. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by Anonymous Coward · · Score: 1

    Its a feature, or at least a really bad design flaw that no one has stumbled upon/abused up until now.

    Or so we have to assume. A real blackhat isn't going to advertise his source of income so that patching makes his goldmine obsolete. The fact that we only see dumb, recycled exploits over and over again may very well be caused by an evolutionary proces. (Nice, huh, how I can get an ID remark even into a Microsoft topic? ;P)

    What I'm saying is: there is a very real possibility that this exploitable bug/feature has already been used to enter your network. To rob you blind, change that one number in a CAD-assisted engineering plan for that new super-structure/nuclear reactor, kill that one patient, who will tell?

    The rest of the story I'll leave to your imagination, lest I be accused of bashing.
  87. anyone else get bitten loading the patch? by Anonymous Coward · · Score: 0

    My XP PC (which has been in suspend mode for over a week) woke up and I loaded the new Java runtime and Microsoft security patches. The patches took way too long long to load and CCAPP.EXE refused to exit when shutting down. Restarting got me to a login screen with no user icons - my user account had been deleted! Now I get to try to find and restore all my old user files and registry entries. Joy, joy.

  88. GIMP issues by cvd6262 · · Score: 1

    Has anyone else noticed a delay when saving a file in the GIMP after applying the patch?

    --

    I'd rather have someone respond than be modded up.

  89. i was under the impression by petermgreen · · Score: 1

    that the unregister workaround only cut off some of the nastier attack vectors but not nessacerally all of them.

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  90. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by Viriatus · · Score: 0

    For example, old software from industrial robots. In my university there's some robots that work only on DOS. They have there some old PC's with Windows 95. The program runs in DOS mode. But of course they are not connected to the internet. yeah those robots are old but are fun to play with. I guess they don't want to spend a lot of money on new robots that we can easly damage :D.

  91. Already been patched long ago by Anonymous Coward · · Score: 0
  92. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by Anonymous Coward · · Score: 0

    I am using 5.10 Ubun oh wait...

  93. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by gemtech · · Score: 1

    CONSPIRACY THEORY: This is how they will finally get everyone to upgrade, from fear. But I will continue to use my WIN98SE box, running my favorite PCB CAD program.

    --
    Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
  94. Absolutely Ridiculous by ClamIAm · · Score: 1
    Even the discription Microsoft gives on Windows Update is just absolutely mind-boggling:

    A remote code execution security issue has been identified in the Graphics Rendering Engine that could allow an attacker to remotely compromise your [Windows computer].

    I mean, what's next? Opening a mis-formed text file with Notepad gives an attacker root access?

    But I think the more serious problem is that MS doesn't release patches when they're ready, except in cases when it's very serious (like this). What if this had happened a week from now, but wasn't discovered for yet another week or something? Would they still release early? End-of-life schedules also present problems, with older releases often being affected by new vulns but not being patched.

    1. Re:Absolutely Ridiculous by Zhe+Mappel · · Score: 1
      I mean, what's next? Opening a mis-formed text file with Notepad gives an attacker root access?

      What's ahead is even worse, I'm afraid.

      Removing the shrinkwrap from the Windows Vista box will dangerously elevate levels of static electricity, which in turn will cause your hair to stand up, thus scaring your dog who will reply by beginning to hump your leg. This will excite ions whose interstitial harmonic resonances will cause all your passwords to be mailed to a Czech porn site that, not coincidentally, will use them as a cipher to decode the current US nuclear launch codes. The Czech porn site is a sideline for a major producer at Fox News who lost his penis attempting congress with a food processor, and, understandably, blames liberalism. He'll use his influence with a Pentagon bigwig known to favor military strategies for expediting the Rapture, and together they'll blackmail a meth addict manning a missile silo in North Dakota to go all Strangelove on Iran. That'll start World War III, which will be over before you can finish installing Vista.

      So you see, monthly patches are sufficient.

  95. Eat Me by Anonymous Coward · · Score: 0



    Eat me deep

  96. All it takes is a little care... by Anonymous Coward · · Score: 0

    It amazes me that people still go out of their way to make themselves as vulnerable as possible. My Antivirus progam was catching these WMF exploits well before this patch was released - does no-one run AV software? Finally, machines with DEP enabled (software or hardware) were, according to MS, not vulnerable to this attack either.

    I can remeber when getting a virus via an image was just an urban myth - well done MS for making it a reality.

    1. Re:All it takes is a little care... by slowbad · · Score: 1
      My Antivirus progam was catching these WMF exploits well before this patch was released

      You can log in to Yahoo webmail for the first 8 hours of a major outbreak
      and still download known=bad attachments.

      Hotmail webmail currently blocks 49 file extensions, but WMF is allowed.

      And last time I looked, Norton's 7.x and 8.x Corporate clients show new
      DATs available once a week on Wednesdays only after 5pm EST. Hell,
      Symantec had to get their own house in order last week (RAR) anyway.

  97. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by NutscrapeSucks · · Score: 1

    I'm pretty sure that IE 5.0 for Windows 3.1 can.

    --
    Whenever I hear the word 'Innovation', I reach for my pistol.
  98. have to run 3.0 by r00t · · Score: 1

    Windows 3.0 was the last release with 8088 hardware support, you insensitive clod.

  99. Re:Win 98, Win 98 SE, Win 98 ME by IEBEYEBALL · · Score: 1

    Why? I have an older computer. Win 98 SE does everything I need just fine. Why do I want to buy a new computer just so I can pay Microsoft for a newer operating system that I don't need?

    --
    -- SKYKING, SKYKING, DO NOT ANSWER.
  100. The patch was leaked by Anonymous Coward · · Score: 1, Informative
  101. What happened when I installed the patch by kalbzayn · · Score: 1

    I noticed the little shield icon so started clicking to install the patch. When it was done, it told me that I should reboot, so I did. I wasn't paying attention when the computer came back on, so it went into the default OS. So now, I'm happily typing away in Linux. Which reminds me that I need to change the default OS back to Windows before my wife notices.

  102. Executive Summary by Anonymous Coward · · Score: 0
    Microsoft Security Advisory 912840

    "Microsoft has completed the investigation into a public
    report of a vulnerability"

    "Microsoft disclaims all warranties, either express or implied,
    including the warranties of merchantability and fitness"

    "We have issued a security bulletin to address this issue"

    "The information provided in this advisory is provided 'as is'
    without warranty of any kind"

    "For more information about this issue, please review the
    security bulletin"

    "In no event shall Microsoft Corporation or its suppliers be
    liable for any damages whatsoever"

  103. non IE link please by Jbcarpen · · Score: 0

    this may have been answered before, but I have used IEradicator, and I need a link that does not require me to use Internet Exploder to download the patch. Therefore, if anyone could direct me to such a link, I would be gratefull.

    --
    GENERATION 667: The first time you see this, copy it into your sig on any forum and add 1 to the generation
    1. Re:non IE link please by Captain+Chaos · · Score: 2, Informative

      Yes this was also in another post, but here you go:
      http://www.microsoft.com/technet/security/Bulletin /MS06-001.mspx
      I was able to download the XP and 2000 patches just fine with Firefox from that link.

    2. Re:non IE link please by Jbcarpen · · Score: 0

      thank you

      --
      GENERATION 667: The first time you see this, copy it into your sig on any forum and add 1 to the generation
  104. Microsoft Bashing by OpenMynded · · Score: 2, Insightful
    Events like this WMF Exploit only prove two things.

    1. People like to b*tch about everything no matter how good they have it.
    2. Most of the people here would still hate Microsoft even if Bill gave up 75% of Microsoft's yearly profit to fund cancer research. You'd all whine "Why can't Billy give 90%, that evil, crooked b@stard."

    All you Billy-bashing knuckle-draggers can't even fathom the fact that if Mac OSX or RedHat were the top dog in enterprise sales and Microsoft was the undercapitalized weakling, viruses, worms, and spyware would no longer exist for the Win32 platform. Why would the hackers and script kiddies spend all time and effort trying to target only 20% of the market?

    You also don't have the mental capacity to appreciate Microsoft's innovative contributions to the IT industry, either directly or indirectly. Many of our current technologies were spurned directly from the spirit of competition against Microsoft. So MS buys someone out. Why hate MS? Why don't you hate the seller for selling out? You are all just looking for something to whine about.

    1. Re:Microsoft Bashing by fleaboy · · Score: 1

      Glad to see a Microsoft cheerleader back in action. Fixed your exploit did they? I personally don't use Microsoft products because of their illegal business tactics. Their software is, well.....

      --
      Life is a gift. And my Karma couldn't possibly be 'Positive'
  105. Engineers? Please do not abuse the term by SmallFurryCreature · · Score: 1
    REAL engineers are responsible for what they produce. They got to sign their name to any design/product they produce. Do not put the QA monkeys at work at MS in the same category. That is like calling the guy who sells you miracle herbs to extend your penis a docter.

    Oh and if you claim the they are really engineers then that is good. We should be able to find the person that signed of on this wmf code and promote him to head of software development at MS.

    Cause lets face it, nobody has even been fired for putting bugs in MS software.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Engineers? Please do not abuse the term by javaxman · · Score: 1
      We should be able to find the person that signed of on this wmf code and promote him to head of software development at MS.

      I'm not saying they're that good, I don't know them... but we probably could find the project manager, product manager, engineering and QA managers who worked on this patch, if we really had enough clout to shake that information out of Microsoft. And they might actually be that good.

      Honestly, I'm going to guess that in this case, some QA manager basically had to sign off on the patch after a bare minimum of planned testing because everyone from the CEO on down ( and everyone in every IT department using MSFT products everywhere ) were jumping up and down demanding this patch ASAP. But I do think that it was probably 'ready' several days before it's release was announced, and that the difference between the third-party security expert's patch and the MSFT patch in terms of delivery boils down to having had that "minimum" amount of testing performed ( and maybe one rev of the patch to fix a bug that was found... maybe... )

      However, I'm going to assume that many of the 'QA monkeys' at Microsoft do deserve the title 'engineer', and do designs and make real test plans and take pride in their work, even if their effort isn't recongnized as valuable by the managers and developers around them. After many, many years in the software industry, I've found that software is not released with bugs because of the engineers- they've usually found most of the bugs and know what needs to be worked on- it's released anyway because the company has marketing and sales obligations to push a new product before the end of some arbitrary market-based ( often end-of-quarter financials based ) point in time.

  106. Re:Microsoft Bashing - spirited defense but ... by chawly · · Score: 1

    You should look up the word "spurned". I think that the word you want might be "spawned". At any rate cowboy "spurned" has got nothing to do with spurs.

    --
    How many beans make five, anyhow ? ... Charles Walmsley
  107. How bloody typical .......... by Gorshkov · · Score: 2, Informative

    Thank you for your interest in obtaining updates from our site.
    To use this site, you must be running Microsoft Internet Explorer 5 or later.
    To upgrade to the latest version of the browser, go to the Internet Explorer Downloads website.


    How bloody typical ..... I use firefox so I don't have to use their crap any more than I have to, but I have to use their crap in order to fix another piece of their crap .....

    1. Re:How bloody typical .......... by OpenMynded · · Score: 1
      No you don't. I used Firefox and went to http://www.microsoft.com/technet/security/bulletin /ms06-001.mspx and had no problems downloading the update.

      Look, if you think it's crap, then why are you using it? If you don't like it, stop your incessant whining and do something about it. Go to Linux RH or buy yourself a Mac. Then you can go flood the Mac/Redhat boards with your complaints.

  108. WMF Patch killed Firefox! by jhall · · Score: 2, Informative

    Has anyone else noticed that after installing the "WMF Patch" you now have a "My Websites on MSN" site in your "My Network Places" and that Firefox v1.0.7 now hangs on load? That's a good way to win the browser war. Great job Microsoft!

  109. Sadly yes by steve_l · · Score: 1

    word and write files can host and render WMF files internally. the fact that nobody has written a file that uses that as an attack vector doesnt mean that it isnt possible, only that there is such an easy (and consistent) route to owning winxp that nobody has bothered with the older systems yet.

    After all, if you are a bot author, would you rather build and test for winXP or support legacy Win98 boxes with their weaker networking stack, device driver problems, etc. Think of all the support calls :)

    1. Re:Sadly yes by Derek+Pomery · · Score: 1

      Right. That was my point.
      * it has been established this is due to a file format decision goes back to Windows 3.0
      * it allows arbitrary code execution

      For Microsoft to call it non-critical on older platforms just because no one has
      tried exploiting it yet is just irresponsible.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    2. Re:Sadly yes by Pii · · Score: 1
      I didn't mean to suggest that I don't think it should be categorized as high/critical priority by Microsoft... I'm only relaying the reasons they've provided for why it isn't.

      I think they're bullshit reasons too.

      --
      For those that would die defending it, Freedom
      has a sweet taste that the protected will never know.
  110. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by aug24 · · Score: 1

    Wow. I'd say it's not a feature, or a design flaw, it's actually a designed in back door to execute arbitrary code contained within the WMF object.

    It proves the point so many of us have observed: Friends don't let friends put Windows on networks. Its 'trust everything' design should have been revisited at the same time as MS built their first network stack.

    Justin.

    --
    You're only jealous cos the little penguins are talking to me.
  111. Re:Microsoft Bashing - spirited defense but ... by OpenMynded · · Score: 1

    Yes, chawley. Thank you for pointing that out. Now let's see if people can get past one inappropriately used word and focus on the point of the comment.

  112. Re:Win 98, Win 98 SE, Win 98 ME by msobkow · · Score: 1

    To paraphrase:

    I have an old car. It gets me around town. Why do I want to buy a new car just so I can pay Ford/GM/Chrysler/??? for a newer car that I don't need?

    Except that your car is so old it doesn't really have keys or anti-theft protection, so criminals keep taking it and using it to try to run other people off the road, litter the streets with spam, or create traffic jams of old beaters tying up the interstate so no one else can use it (DOS attack). It's so old that it's just not safe any more, and should not be allowed on public roadways.

    Besides, car prices have changed. That new car costs about half of what your old monitor did way back when... ;)

    --
    I do not fail; I succeed at finding out what does not work.
  113. Re:Microsoft Bashing - spirited defense but ... by chawly · · Score: 1

    Oh but I did, my dear good sir, I quite got your point (just had to open my mind a bit) thought I'd point out the mistake, though. Must admit I thought it was a cowboy getting a bit carried away. For the record, I quite agree with you - but I did think that the mistake would cause a smile. Worth underlining it for the smile, I thought. Didn't mean to bother anybody. Mes excuses.

    --
    How many beans make five, anyhow ? ... Charles Walmsley
  114. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by jonadab · · Score: 1

    > but really, if you're using 3.10 as a desktop...

    No, you see, I never upgraded to 3.1, because it requires a 386 CPU...

    --
    Cut that out, or I will ship you to Norilsk in a box.
  115. Re: every Windows operating system since 1990 by some+guy+I+know · · Score: 1
    Hyppönen said the vulnerability is supposed to hit "every Windows operating system since 1990".
    The official Microsoft bulletin says it affects systems going back to Windows 98.
    Since my computer is running MS-Windows 95 (when it runs MS-Windows), it's safe.
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  116. Re:1st Party did not patch vulnerability either, t by CFrankBernard · · Score: 1

    Ooops, sorry. I was reading non-threaded.

  117. Re:2000, XP, 2003, but no 3.10, 3.11, 95, 98, or M by toddestan · · Score: 1

    No, you see, I never upgraded to 3.1, because it requires a 386 CPU...

    That's not true. Windows 3.1 runs happily on a 286 provided you have enough ram. You just don't get the benefits of "386 Enhanced Mode".

  118. Re:Win 98, Win 98 SE, Win 98 ME by IEBEYEBALL · · Score: 1

    Yes, it does. My Win 98 SE box is behind a stout hardware Linux firewall that has a shitload of ports blocked off. The Win box itself has a software firewall, grisoft avg, and several malware/spyware removers. I simply won't run a Windows box on an external IP address, no matter what version of the operating system. I just don't trust Microsoft. I also have a Win 2K Pro box btw and I take the same precautions with it.

    --
    -- SKYKING, SKYKING, DO NOT ANSWER.
  119. Re:Win 98, Win 98 SE, Win 98 ME by IEBEYEBALL · · Score: 1

    And yes, I have a 1995 Jeep Wranger. It gets me around town. I don't want to buy a new Jeep because the stuff being put out today by Chrysler sucks. I've added anti-theft protection to my 1995 Wrangler. I keep it in tip top mechanical condition so it's safe. And a new jeep costs a shitload more than what I paid for my Jeep in 1995.

    --
    -- SKYKING, SKYKING, DO NOT ANSWER.