I'm not sure this is that big of a deal, while it is legacy, when i tested it on a coworkers laptop just to screw around at the office, It really didn't do anything. While i didn't continually blast him with packets, while his CPU was at 100%, it didn't completely effect his usability, and as far as the instability comment that was made either here or on the SANS site, we haven't noticed that either.

All in all, this is lame. While scripting it and getting inside a firewall could cause a problem, all you have to do is shut down the offending computer, or unplug it from the network, and all is back to normal. I didn't read the post above me when i was typing this, but in response to that, isn't it a simple IPSec rule to disable that? Sorry I don't manage too many servers, and their Win2k so I'm not in position to talk. This is just an outside perspective.

While alot of home users might not be behind a firewall, a common instinct with most people is to shut down the computer when it starts getting slow. If the attacker keeps blasting them with packets, their next major reaction is to either call someone, or simply shut it down and not go back to it for a day or at least a few hours. by then, the attacker is probably bored, or thinks that he accomplished his feat and goes on to harass someone else.

While I agree that its 8 years old, and its freakin stupid its there in the first place, all in all, this really isn't all that much to be worried about. I think the major impact of this is that, who knows what other sploits from back in the day still work. If they let one slip thru, then their could be more, and they could be worse.

Maybe i'm just missing something. And I really hate MS, but maybe they tested in the lab, and came to the same conclusion i did. this is lame. It serves no better purpose than to screw with people at the office for fun, or to cause some trouble in LAN parties.