Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Microsoft's "Dead Cow" Patch Was 7 Years In the Making

Posted by timothy on Wed Nov 12, 2008 02:57 PM
from the were-they-lean-years-or-fat-years? dept.
narramissic writes "Back in March 2001, a hacker named Josh Buchbinder (a.k.a Sir Dystic) published code showing how an attack on a flaw in Microsoft's SMB (Server Message Block) service worked. Or maybe the flaw was first disclosed at Defcon 2000, by Veracode Chief Scientist Christien Rioux (a.k.a. Dildog). It was so long ago, memory is dim. Either way, it has taken Microsoft an unusually long time to fix. Now, a mere seven and a half years later, Microsoft has released a patch. 'I've been holding my breath since 2001 for this patch,' said Shavlik Technologies CTO Eric Schultze, in an e-mailed statement. Buchbinder's attack, called a SMB relay attack, 'showed how easy it was to take control of a remote machine without knowing the password,' he said."
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Maniacal (12626) on Wednesday November 12 2008, @02:59PM (#25737775)
    So that's how they came up with the name 'Windows 7'
  • by Anonymous Coward on Wednesday November 12 2008, @03:03PM (#25737813)

    ...and boy are my arms tired.

    P.S. I'm dead.

  • by WillAffleckUW (858324) on Wednesday November 12 2008, @03:06PM (#25737877) Homepage Journal

    I mean, seriously, most of us have written it off, and it makes bad business sense too.

    At work we've cancelled plans to use Win7 and WinVista and are moving to all Linux where we can, just from a staffing level perspective.

    • by HerculesMO (693085) on Wednesday November 12 2008, @03:20PM (#25738059)

      Yes, lots of people still do.

      Makes little business sense right now to go to Win7/Vista, but XP is still a smart move for most people.

      It's too bad Slashdotters here are so entranced with the platform, they forget what it's supposed to delivery. I don't really care what OS is on the desktop, so long as it allows us to achieve what we are trying to do. Usually, it's the software that does that, not the OS.

      • by Sancho (17056) * on Wednesday November 12 2008, @03:27PM (#25738171) Homepage

        Of course, if the OS is fighting you all the way while you're trying to work with the software, that's a problem.

        • by HerculesMO (693085) on Wednesday November 12 2008, @03:33PM (#25738261)

          From my experience, the Linux folks that try to work in Windows just simply don't know WTF they are doing.

          Likewise, Windows Admins who work in Linux don't know either.

          It's always easy to curse the platform if you don't have the knowledge. I've built stable environments out of Windows and out of Linux, and they all serve their purpose with perfectly fine uptime. Just a different delivery platform for different things.

          • by Sancho (17056) * on Wednesday November 12 2008, @03:40PM (#25738351) Homepage

            I'm not specifically referring to tasks which are "hard to do" in the OS--I'm referring to the incessant stream of vulnerabilities in various components that makes working with Windows a virtual minefield.

            • by HerculesMO (693085) on Wednesday November 12 2008, @04:14PM (#25738781)

              In the 7 years as a Windows Sysadmin I've seen my job getting easier and easier by taking a few proactive steps to corporate use of Windows.

              For server use, it's perfectly fine. I have a Windows file cluster running over a year without an downtime, but we've taken cluster members offline for patches in turn, and failed back to the alternate which is a net of 0 downtime.

              We use strict policies on the desktop, and don't allow users to do things that are going to cause problems. Mostly, this includes *not* giving them administrative rights, though we do delegate some things out.

              It's like any other system. The problem is that Windows is so large an ecosystem, and so many folks that 'represent' Windows sysadmins pretty much suck at their job, or are MCSEs on paper and not in practice, then it does a disservice to what I feel is a perfectly fine OS for daily use, and corporate use. I have no 'virtual minefield' because I know my business well, I know my job well, and I perform well in bringing harmony between them (the business and the IT use).

              It's like ANY system (*nix included), because if you have an incompetent sysadmin, you will have problems on your domain and infrastructure. If you have a competent sysadmin, you won't see anything wrong. Our users are largely very happy, and that's done by internal auditing (mandatory surveys, as we represent 19000 employees country wide), and consistently the 2500+ userbase I work with and for rank me highest of the family of companies I work for in their satisfaction in their computing needs.

              Again, it's not the platform at fault, it's the admins around it. If you feel Windows is a virtual mine field then it may indicate your talents lie elsewhere (*nix), and as such should keep to the business you know, rather than tell folks who run Windows successfully that they have inherent problems at hand they aren't aware of.

              • by malkavian (9512) on Wednesday November 12 2008, @04:58PM (#25739343) Homepage

                Hear hear. I've been running UNIX and Windows in admin capacity since the early '90s. The biggest problem I've seen at the moment is caused by marketing. Microsoft just refuse to stop advertising Windows servers as being so simple the cat could administer it.
                With that message on the table, HR departments get the idea that all it then takes to administer servers is one cat and a magic wand. So they create low paid jobs for 'admins' that don't actually know much about administration (as it's so easy, who actually needs skills in it 'eh?).
                UNIX tends to get better results overall, largely because it's seen as a skilled job. They pay the money, they require that you know what you're doing.
                Where you get admins that know the detail on Windows to the depth that UNIX gurus know UNIX, comparable results are obtained.

                Now, if only Microsoft would stop telling suits that all they need to administer Windows is someone with one finger and half a brain, then the rep. of Windows would increase dramatically. However, there's money to be made today by churning out an MCSE who two weeks ago didn't know what the power cable plugged into. Who cares about the future of the platform when you can advertise tomorrow with a new glossy pamphlet, and make money today? Well, apart from the people who really understand system administration, and hey, what do they know?

                • by Sponge Bath (413667) on Wednesday November 12 2008, @05:40PM (#25739933)

                  ...stop telling suits that all they need to administer Windows is someone with one finger

                  Damn skippy! Alt-Ctrl-Del takes three fingers.

                  • by conlaw (983784) on Wednesday November 12 2008, @06:24PM (#25740491)

                    Windows is GUI based to be sure, but there are behind the scenes things (registry, hosts files, policies, clustering, etc) that is not as intuitive as people think it may be. That's also where a LOT of problems occur, and cause the BSODs and other things that the *nix fans love to jump at.

                    Yes, my penultimate reason for leaving Windows was all of those hidden problems like "why is xxx.dll using 92% of my capacity? and WTF is xxx.dll anyway?" MS would never tell anyone the answers so you had to go to all of the forums where people volunteer to help you, but first you have to download and run a spy seeker, an ad finder, a virus detector and "Hijack this." BTW, I have great respect for these volunteers but they shouldn't be needed in a system that I paid for.

                    Just to forestall questions, my ultimate reason for leaving was when I read what Microsoft Genuine Advantage was going to do, rather than blindly pushing the download key so that I could get this "advantage."

              • by Thaelon (250687) on Wednesday November 12 2008, @06:33PM (#25740603)

                What format was that survey in?

                I recently had the opportunity to design a survey. And preemptively learned from the mistakes at UPS [surveycompany.com].

                We started out with a ton of questions we thought were good, then scrapped the idea and asked three open ended questions with big free form text fields.

                Another group went ahead and asked a bunch of continuum and multiple choice questions.

                In their survey everything looked peachy.

                In ours (the freeform one) results were considerably less favorable, and considerably more useful.

                Usefulness can be lost especially easily when you simply boil the continuum questions down to percentages. What if that mere fraction of a percentage of your employees that are extremely dissatisfied are crucial to it's function? Or if you didn't ask the right questions?

                It's really easy to create a survey that tells you absolutely nothing useful.

              • by kwabbles (259554) on Wednesday November 12 2008, @08:12PM (#25741561)

                My #1 beef with Microsoft is that they market it so that every small to medium business owner thinks that everything will all run together happily on one box all "plug-n-play" and snuggly whirring away on the floor of their office closet.

                I have the hardest time convincing users that they cannot run their 20-user network on one SBS 2003 server, with Exchange (running OWA and OMA), running their heavily-accessed SQL database, sharepoint, anti-virus server software, backup software, and company file and printer sharing to 5 multi-function copiers and expect 5 9's of freaking uptime.

                This is how it is marketed. This is what the end user expects when shopping for a Microsoft solution. You tell them that they'll need at least 3 separate boxes, Server, Exchange, SQL, etc all separate, RAID and ideally a failover system and an excellent firewall for the remote access they look at you like you're nuts. So they buy it and have it set up their way, it works like hell for a year, then they end up paying in the end to have it done again the right way (and more this time, because they have to now migrate off of their old system).

                And the Microsoft money machine chugs on.

          • by stevied (169) on Wednesday November 12 2008, @04:20PM (#25738859)

            I've hacked an interesting little solution together for my household, which I'm sure would scale. I've been using Linux for about 13 years, and have forgotten more tricks than most people know. Over that time I've done a certain amount with Windows, too, but the lack of a rich toolset and open / free documentation and source always put me off spending too much time on it. I understand things are a bit better now on those fronts, but I chose where to invest my time ages ago. I've certainly not bothered about keeping up to speed, have no experience with Vista, Office, 2007, etc.

            Anyway .. I have to provide a Windows environment for a family member who's really not up to learning anything new. I wanted to be able to manage it, secure it, control changes to the configuration, etc., etc., and eventually hit on the idea of just running XP inside VBox on Ubuntu. It starts automatically, changes to the main Windows partition are discarded on each shutdown, and I can do all my management with ssh (and occasionally rdesktop if I need to actually fiddle with Windows, which is rare.) Performance is fine even on old hardware.

            Virtualization on the server is obviously mainstream now, and I guess many users are running virtualization software themselves to provide access to apps on other platforms and run old software. I haven't seen much about using virtualization as a platform for managed desktops though, and I reckon it has some advantages: moving images between machines when hardware fails or users move departments; change control; configuration testing, etc., etc. Knowing you've got the exact same disk image in use on a herd of workstations, regardless of hardware, seems like a good thing for peace of mind ..

        • Re: (Score:3, Insightful)

          If you've used Windows in a corporate environment and still feel that way, there is something wrong with your organization. I've been with my current company for just over a year now and yesterday I called the help desk for my first Windows related problem. It's stable, period. Now, all the antivirus, security, firewall etc they install makes the thing so slow it's awful to use, but that's beside the point.

          One thing is for sure, though. I don't want to make an 'Impress' presentation and send it to a clie
          • Re: (Score:3, Insightful)

            Actually, I thought that was specifically the point. If people hate using their computer, then you're doing something wrong.

            It's about getting the job done, but Microsoft has consistently been the roadblock. Microsoft is the barrier to compatibility. They're the roadblock to having everything "just work". The Windows monopoly has to end before we can move forward again.

          • by Duckie01 (10586) on Wednesday November 12 2008, @04:07PM (#25738683)

            If you've used Windows in a corporate environment and still feel that way, there is something wrong with your organization. I've been with my current company for just over a year now and yesterday I called the help desk for my first Windows related problem.

            Perhaps the gp was on the other end of the line, dealing with the nightmare to keep the rest of the organization including you, clear from it. In other words, your experience with your office desktop computer might say more about the quality of the IT department that installed the OS than about the flaws in the installed OS.

            It's stable, period. Now, all the antivirus, security, firewall etc they install makes the thing so slow it's awful to use, but that's beside the point.

            No, that is *not* beside the point. You see, if you *need* to bog down your OS with third party software to keep it working reliably at all, I'd say that the flaws in this OS are exactly what causes your pc to slow down to the point that it's awful to use.

            One thing is for sure, though. I don't want to make an 'Impress' presentation and send it to a client unless I'm sure they are going to be able to open it in Powerpoint.

            Yeah or in something else they might have, like Impress ;) I actually don't know Impress, btw. But I get your point.

          • by Tubal-Cain (1289912) * on Wednesday November 12 2008, @04:25PM (#25738915) Journal

            One thing is for sure, though. I don't want to make an 'Impress' presentation and send it to a client unless I'm sure they are going to be able to open it in Powerpoint.

            It may give you peace of mind to know that MS released the specs on their binary formats [slashdot.org] in late June, so the OOo team had about 2.5 months to fix their implementations in version 3. If they didn't manage that, they should have them in the next release.

    • by heffrey (229704) on Wednesday November 12 2008, @03:38PM (#25738325)

      Hardly anybody still uses Windows, it's dying out.

      • Re: (Score:3, Funny)

        by Anonymous Coward
        Good riddance, it's been a total pane since day one.
    • I do. And I like Vista too.
      • by Cowmonaut (989226) on Wednesday November 12 2008, @04:54PM (#25739283) Homepage
        How, HOW is this Flamebait? I happen to like Vista as well, now that SP1 is out and the majority of my driver issues are resolved. In fact, literally the only issue I have with my system currently is a VERY small sector on my hard drive or bad memory space on a single stick. I'm not sure which, I occasionally (3 times a month) blue screen due to an issue relating to one or the other. For all I know, its really my motherboard since memtest and SMART test my hardware fine.

        Just because YOU don't like Vista doesn't mean others don't. On my desktop I happen to think my system runs smoother and faster and is easier to fix than with XP. To each his own, like several other +5 Insightful in this thread have mentioned...

  • by Trepidity (597) <delirium-slashdot.hackish@org> on Wednesday November 12 2008, @03:08PM (#25737891) Homepage

    Seven years ago, The Register devastated me with this terrible news:

    It's backward compatibility that has MS in a trap now. "NTLMv2 was created to address many of these issues, and if Windows came configured to use only NTLMv2 these would not be issues, unless the user knowingly opened himself up to allow communication with older operating systems," Sir Dystic noted.
    [...]
    However, if for some reason it's necessary for you to use the many thrilling features of Windows networking without NTLMv2, then there is absolutely nothing you can do but pray.

    Finally, I can use my favorite thrilling NTLM features without giving in and using NTLMv2!

  • SMB? (Score:3, Funny)

    by EraserMouseMan (847479) on Wednesday November 12 2008, @03:09PM (#25737901)
    Could a Windows Server Admin worth his/her salt please explain to us what SMB is, who would use it, and if there was a workaround that made the vulnerability a non-issue?
  • C2MyAzz (Score:5, Interesting)

    by Anonymous Coward on Wednesday November 12 2008, @03:10PM (#25737923)
    Hmm - there was an attack called C2MyAzz that was even simpler than the man in the middle attack. It would just spoof the handshake between client and server. The attacking workstation would watch for client->server message requesting authentication. The attacking workstation would send a packet back to the client before the server, asking the client to send back a clear-text password. Much easier than a man-in-the-middle attack, and it worked well. When it was released, Microsoft's official response was "most organizations use switches and routers, so this is not a problem". Originally released in 2001, IIRC.
  • port 139 (Score:5, Funny)

    by heffrey (229704) on Wednesday November 12 2008, @03:15PM (#25737997)

    Oh well, I guess I'd better block incoming public Internet traffic on port 139 then. That's a shame because it's been so very useful to have an Internet facing SMB share.

  • by girlintraining (1395911) on Wednesday November 12 2008, @03:19PM (#25738043)

    It's always been easy to take control of a machine without the password. Sit down in front of the computer. Now the only thing stopping you is yourself. Oddly enough, that's what keeps most systems up... The fact that the vast majority of people are honest, decent folk. That, and they don't know what a null pointer is.

  • by Tomun (144651) on Wednesday November 12 2008, @03:25PM (#25738153)

    "I've been holding my breath since 2001 for this patch"

    With lungs like that he should try free-diving!

  • by 140Mandak262Jamuna (970587) on Wednesday November 12 2008, @03:31PM (#25738241) Journal
    From the article: To make matters worse, the SMB flaw was already publicly disclosed prior to Tuesday's updates, Microsoft said.

    What made it worse? Taking 8 years to fix it or disclosing it before the patch was released?

    Further it is not a bug at all. It is essentially badly designed protocol having a hole and instead of abandoning it and making users upgrade, MSFT left this hole open for 8 years. All the in the name of backward compatibility. Why has backward compatibility trumped security for 8 years? It not surprising no one takes MSFT's statements about its commitment to security seriously?

    • by UnknowingFool (672806) on Wednesday November 12 2008, @03:43PM (#25738385)

      From the article: To make matters worse, the SMB flaw was already publicly disclosed prior to Tuesday's updates, Microsoft said.
      What made it worse? Taking 8 years to fix it or disclosing it before the patch was released?

      This is MS modus operandi. You know all those MS based studies that say that MS fixes bugs faster than Linux. Well we never really believed them but they are technically true. See MS only counts the time between when they publicly disclose a bug and when they patch it. They don't count the time between when they find or are informed of the bug. With Linux people the whole process is more transparent. When bugs are discovered in Linux, they are almost disclosed at the same time. So this 8 year old bug will appear on all MS studies as only taking a few days rather than 8 years.

  • by Beelzebud (1361137) on Wednesday November 12 2008, @03:32PM (#25738253)
    How many people were actually a victim of this exploit? Is there one documented case of an electronic break-in because of this exploit?
  • by pcolaman (1208838) on Wednesday November 12 2008, @03:34PM (#25738277)
    So does that mean we can expect a Dead Cow Level to be hidden in an included Windows 7 app, a la Flight Sim hidden in Excel 97.