Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Microsoft Bracing for Worm Attack

Posted by CowboyNeal on Fri Aug 11, 2006 08:01 AM
from the red-alert dept.
10010010 writes "A network worm attack targeting a critical Microsoft Windows vulnerability appears inevitable. The flaw is easy to exploit, as evidenced by the quick release of an exploit module for HD Moore's Metasploit Framework. Within hours of the Patch Day release Tuesday, two pen testing companies (Immunity and Core) created and released 'reliable exploits' for the flaw, which was deemed wormable on all Windows versions, including Windows XP SP2 and Windows Server 2003 SP1."
+ -
story
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 Anonymous Coward on Friday August 11 2006, @08:03AM (#15888368)
    This article mentions the 23 patches that Microsoft released. It then goes on to say:
    Just days after the Redmond, Wash., software maker issued the MS06-040 bulletin with patches for a "critical" Server Service flaw, Microsoft's security response unit is bracing for the worst after exploit code that offers a blueprint for attacks began circulating on the Internet.
    And mentions that
    Aitel's company was able to reverse-engineer Microsoft's patch and create a working exploit in less than 24 hours.
    So are they saying that Microsoft is preparing for fall out from a new exploit that utilizes hastily written code from the latest series of patches? Is that what the pen companies reverse engineered? Or is Microsoft waiting for all the people who didn't patch their systems to be hit with what the DHS warned about and Microsoft fixed?

    I'm confused and I'd like to know if my building's Window's administrator needs to be put on suicide watch. He was up all night last night. From what it sounds like, he spent all that time trying to increase the security of our machines when he was really just altering the application so that the virus that came out 24 hours later would be able to attack the machines ... there is one non-Windows machine in my lab. I think I'll use that one today.
    • by Anonymous Coward on Friday August 11 2006, @08:07AM (#15888384)
      you can get the patch for the patch here [ubuntu.com]
      • Damn straight Baby! I used to use Fedora but a co-worker turned me onto Kubuntu (a KDE version of Ubuntu). At first, getting used to a Debian based distro was tough but I quickly realized that I really didn't have to do my makes or check for dependencies and a ton of the other stuff that can just be a constant annoyance and reduces consumer uptake of Linux as a Desktop.

        I have it installed on my Mom's computer and she loves it! Instantly detected her new digital camera my brother got her, her scanner, her pr
        • by advocate_one (662832) on Friday August 11 2006, @11:51AM (#15889918)
          I now run Ubuntu at home and at work. When all the windows systems are getting patched, updated crashing or just dying (my bosses computer needs a re-install this morning), I can just keep plugging away.

          that's the real pisser though isn't it... everybody else can use the "my computer's playing up" excuse when they're late with some work... us Linux users can't

      • And you can get the patch for Ubuntu here [openbsd.org].
    • by Anonymous Coward on Friday August 11 2006, @08:15AM (#15888439)
      It wasn't 23 patches: it was 12 patches that covered 23 vulnerabilities.

      Yes, it's worms exploiting the MS06-040 vulnerability that they're worried about.

      As long as you're properly firewalled from the rest of the world it can't get in but you should still get everything patched in case the worm gets inside your firewall e.g. as a trojan.
    • by Anonymous Coward on Friday August 11 2006, @08:28AM (#15888516)
      They looked at the patch to find what is being patched, so now they know how to exploit the bug that is fixed by the patch. If your admin updated every Windows computer, you should be fine. The millions of unpatched systems on the internet however will most likely be wide open and added to botnets in a couple of days. Consequently even the users of well-administered Windows computers and other operating systems will feel the fallout of this vulnerability.
    • So are they saying that Microsoft is preparing for fall out from a new exploit that utilizes hastily written code from the latest series of patches? Is that what the pen companies reverse engineered?

      Wrong conclusion I think. More likely the reverse engineering is comparing the patched and unpatched code and actually working out what the exploit is, then writing the code to use it. (this is why the behaviour of the Rails team holding back details of their exploit is rather weird; especially when the sourc

    • by Anonymous Coward on Friday August 11 2006, @08:34AM (#15888544)
      The fix for MS06-040 is KB921883, which is part of the recent batch of critical updates from Microsoft.
      TFA is confusing because it makes it appear as though the latest MS updates *cause* this vulnerability, while in actual fact they *fix* it.
    • Look, whatever the article says, it probably makes sense to ban all liquid or gell substances from any building that has Windows PCs, make all people stand in rediculously long lines to have their pocket books and napsacks security-checked for 8.5" floppy disks carrying said exploit, and even perhaps start a secret list of people who are banned by name from actually accessing a PC at all. I recommend the first name be John Smith, that bastard.

      Further, we should probably ban anyone that has dirt on their shoes, because I hear worms like dirt.

      Saftey first people. It may be an inconvenience, but it's all about your saftey, and the saftey of democracy across the world. We will prevail over the security-exploiters.
    • by TheGhostOfDerrida (953992) on Friday August 11 2006, @09:34AM (#15888929)
      I tried to read the article, but it got a little confusing... is this a worm for a patch? A patch for a worm? A patch for a patch? A worm for a patch for a patch? a patch for a worm for a patch for a patch? A worm that patches? A patch that worms? Patches for worms? Does my dog (patches) have worms? I lost interest. And I think the TV is on...
    • Immunity RE'd the patch to find the original vulnerability. The exploit attacks unpatched machines. Sorry if you were being sarcastic or weird or something (I find it hard to tell the difference.) Anyway, CANVAS (which costs mucho dineros) is not the problem. I'd be more enclined to worry about the (Free) Metasploit Framework [metasploit.org] exploit, by H D Moore - it only works on XP SP1 , W2K3 SP0 and W2K, but there are probably still lots of machines out there in those categories. You may remember Mr Moore, he it was w
  • by $RANDOMLUSER (804576) on Friday August 11 2006, @08:07AM (#15888382)
    From TFA:
    In most enterprises, Pescatore said the use of firewalls and the automatic blocking of TCP ports 139 and 445 should help mitigate the risk. However, he cautioned against IT administrators letting their guards down.
    If you have 139 or 445 exposed to the Internet, you've already been infected with something.
    • by 140Mandak262Jamuna (970587) on Friday August 11 2006, @08:30AM (#15888530) Journal
      Well, In almost all companies and most homes the ports 137-139 and 445 are blocked at the firewall. But internally these ports are open otherwise file sharing/printer sharing inside the network is impossible. True, it wont be serious as long as the firewall holds. But all it takes is one home user bringing an infected laptop to work and plug it in and all hell breaks loose. I had an old NT4.0 machine just to support old releases of our product and for debugging. A salesman from Taiwan came in plugged his laptop in and I was hosed. Worse, the worm was probing rest of the corporate network so seriously that network traffic slowed to crawl in the company. All the top management knew was that I had an unpatched old computer in the network and compromised the company intranet and lost half their work day.

      How easy it is to bring an infected laptop and plug it in behind the firewall? Our salesmen travel all over the world, plug into untold number of hotel intranets and wi-fi cafes. They leave these two ports open when plugged into company intranet. Do they always remember to close these ports when they work in an untrustable network connection? Chances of infection are great. Chances of them bringing the infection behind the firewall into the corporate network is great. I would not hastily dismiss it nonchalantly.

      • by walt-sjc (145127) on Friday August 11 2006, @08:49AM (#15888636)
        IMHO, you should not be blocking those ports at the firewall, but rather redirect them to a responder that floods the return path with copies of the Ubuntu ISO. Run QOS on your outbound and set it at a lower(est) priority than your normal traffic so it doesn't impact you.
        • by g-san (93038) on Friday August 11 2006, @01:35PM (#15890573)
          Nah.... tarpit. Put a listener on those ports (you windows users will have to reboot into linux for this. try it, you'll like it.) Open the connection, read from the channel, then just sit there until the remote end times out. If the worm is stupid enough it will connect back to your PC a few times. That slows them down, and doesn't cause any harm to the net. Or send back three bytes of data every 20 seconds or so... the remote end will buffer it expecting more to come and stretch the timeout even further.
      • by mdarksbane (587589) on Friday August 11 2006, @09:56AM (#15889104)
        Yep, the company I used to work for made a product to stop just that.

        One of the emerging areas in enterprise security is so-called "endpoint" security solutions, that will verify whether a user plugging into a corporate network has
        1) approved virus software with updated definitions.
        2) an approved firewall
        3) Any software updates that the techies have deemed required.

        If you don't, you get shunted off to a quarantined part of the network with instructions on how to obtain the software to make you compliant.

        On the one hand, it sounds like a pain to set up and annoying for the users (and as it usually requires dhcp enforcement can be bypassed by someone who knows the network), and we didn't run in it at our own company, but on the other hand I bet that if they required it at the university I went to the virus problem there would have been much more controlled.
    • by telchine (719345) on Friday August 11 2006, @08:47AM (#15888623)
      I'm a Windows user.

      Can somebody please tell me what the hell a port is? :)
    • by Corbets (169101) on Friday August 11 2006, @08:49AM (#15888639) Homepage
      Unfortunately, it's not that easy. You can (and most everyone does) block those ports at the firewall level. However, people that VPN in or connect via dialup, people who previously connected via the wireless at the local Panera, and either disabled their software firewall or just kept using their machine after that particular piece of software crashed.... they're infected, and when they VPN in, they go right through that precious firewall.

      Every.layer.Every.step.Every.machine.Must.be.secur ed.and.patched.

      It is, unfortunately, the only way.
        • by Gary W. Longsine (124661) on Friday August 11 2006, @10:58AM (#15889578) Homepage Journal
          Any netadmin that allows VPN connected networks full access to their internal nets are idiots who need to get fired VERY soon.
          Your assertion seems obvious on the face of it, but it fails to consider the effects of bureaucracy and complexity, which are real and profound. Many systems administrators are restrained from improving the security posture of networks and systems in "obvious" ways because the business has "requirements" which prevent it. Many of these requirements are derived, in turn, from the tangled complexity of interlocking capability and limitations of various network, systems, and software. Suppose your VPN was established to allow 5000 employees scattered around the country access to hundreds of servers scattered around, too. You might say the architecture is flawed, and it might well be, but if you're the admin and you didn't get to make those decisions then you probably also don't get to just decide to shut down VPN access to Windows port 139, 445 and so forth.
  • It's been a while (Score:5, Insightful)

    by ronanbear (924575) on Friday August 11 2006, @08:07AM (#15888389)
    Since there's been any worms attacking new exploits. I'd even begun hearing from some people that the days of Blaster style attacks are over.

    This should remind Windows users about complacency.

  • by devnullkac (223246) on Friday August 11 2006, @08:08AM (#15888398) Homepage

    OK, maybe I'm just missing an acronym/typo somewhere, but "pen testing?" Will the worms come through my Mont Blanc?

  • by krell (896769) on Friday August 11 2006, @08:13AM (#15888429) Journal
    "The Cyber Gnome here. Denouncer of computer myths. Who needs to download security patches? I don't, and I've never had any prob%$#@@@@#^_@_#@ NO CARRIER"
  • by ericlondaits (32714) on Friday August 11 2006, @08:13AM (#15888431) Homepage
    From TFA:<BR>
    <blockquote>A spokesperson for Microsoft said it is difficult to predict the motives and actions of attackers but insisted the company is "watching round-the-clock" and actively encouraging customers to download the update immediately.

    "We will mobilize if something does happen," the spokesperson said.
    </blockquote>
    They'll mobilize? Mobilize? As in "get the heck out of here"? Or are they calling the [GI]Joes?
  • The Patch (Score:3, Informative)

    by nherc (530930) on Friday August 11 2006, @08:17AM (#15888454) Journal
  • Not quite (Score:5, Informative)

    by jackmama (34455) on Friday August 11 2006, @08:17AM (#15888455)
    which was deemed wormable on all Windows versions, including Windows XP SP2 and Windows Server 2003 SP1

    HD Moore posted a followup to the Daily Dave mailing list admitting defeat on those two platforms:

    Time to eat my words. The wcscpy() destination pointer trick doesn't seem
    doable on XP SP2 or 2003 SP1. I don't believe you can exploit this bug
    for more than a DoS on 2003 SP2/XP SP1. If you have information to the
    contrary, please share.


    All other Windows platforms remain easily exploitable, though.
      • by jackmama (34455) on Friday August 11 2006, @08:36AM (#15888556)
        Windows XP SP2 is the current version of Windows. Has been for almost two years. Aside from Windows XP SP1 all other versions of Windows are no longer supported by Microsoft.

        Well, that's a relief. I was worried that millions of PCs and servers might still be out there running Windows 2000 and NT, and might help propagate some sort of worm. As long as all computers are magically running the currently-supported versions of Windows, I guess we're OK.
  • by krell (896769) on Friday August 11 2006, @08:17AM (#15888460) Journal
    Here's my suggestion for a new Microsoft Windows mascot [halcyon.com]. She's old enough to be public domain, she's tanned, she's rested, she's ready, and she's all patched to hell. All the better that Redmond is located in the vicinity of America's "Emerald City". Please, pay no attention to the borg behind the curtain.
  • by brian23 (962399) on Friday August 11 2006, @08:28AM (#15888520)
    So companies like Immunity reverse-engineer an identified Microsoft patched vulnerability, release an exploit and expect kudos? Impressive as it may sound, I would be more interested to hear of a company discovering a vulnerability and releasing it to Microsoft so it can be patched. If I can't create a virus/worm to wreak havoc on Windows machines, what makes these companies able to reverse-engineer and release the "0-day" exploit? It almost seems unethical. Also, it seems like Immunity and others are trying to make a name for themselves rather than being interested in user security.
    • by OriginalArlen (726444) on Friday August 11 2006, @09:53AM (#15889063)
      So companies like Immunity reverse-engineer an identified Microsoft patched vulnerability, release an exploit and expect kudos?

      Nope, they do it to make money from selling the superb CANVAS product to penetration testers and other security professionals. They couldn't give a rat's ass what some random fucko on Slashdot thinks of it. Sorry to be the bearer of bad news... ;p

  • by geobeck (924637) on Friday August 11 2006, @09:04AM (#15888749) Homepage

    Emperor Shaddam Gates IV admitted today that the high rock formations that ring the city of Arredmond might not be able to repel a full-on attack by the Frehax0rz and their giant worms. Story at 11.

    • Ummm... (Score:5, Insightful)

      by Anonymous Coward on Friday August 11 2006, @08:16AM (#15888446)
      Tell your "neighbor" that if he doesn't want to pay for an OS, that he shouldn't be using Windows.

      But if he's too fucking cheap to get an OEM copy or something and too fucking stupid to bypass the WGA, he should be prepared to have his ass handed to him when this shit hits.

      I'd recommend him going to ubuntu.com, though.
    • Your pirate neighbor should be ok. I'm pretty sure the green parrot on his shoulder will eat any worms. If not, the patch over his right eye is probably the most current out there.
    • by krell (896769) on Friday August 11 2006, @08:25AM (#15888496) Journal
      Your pirate neighbor (what, do you live on a WHARF???) should be able to get around this by launching his Windows in pirate mode. He has to boot to the command line, and then enter WIN.EXE -R -R -R. Also, has he considered the eyepatched system? It might be more useful to him than the "unpatched system" you mentioned.
    • by Professor_UNIX (867045) on Friday August 11 2006, @08:29AM (#15888526)
      Our enterprise file servers run w2k3sp1... Those ports are open on these machines. Basically we have to hope that noone brings infection inside.
      That would be impossible unless you have users that have laptops that they take outside the office or users that browse the web or receive e-mail to their desktops or users that connect remotely from their homes via dialup or VPNs. All very unlikely scenarios in any modern business environment.