By Brian Livingston
Every time Microsoft releases “the most secure operating system ever,” the security flaws just keep on coming. Last week, Microsoft notified users that a hole rated “critical” (the most severe rating) affects not only Windows XP, 2000, and NT 4.0, but also its new, much-vaunted Windows Server 2003 product. Microsoft says Windows Me is not vulnerable, but it didn’t test Windows 9x, which the company no longer supports.
This problem is especially explosive because an attacker can run a rogue program by merely sending packets to a remote machine using any one of various ports. One of these, port 135, is commonly used to send pop-up messages across a network. This feature has been notably exploited in recent months by some spammers, who started sending irritating – but otherwise harmless – ads directly to desktops. Now such payloads threaten to escalate wildly.
Corporations ordinarily block such port access if it originates from outside the firewall. But a malicious person inside the firewall could use the flaw to gain complete control over certain systems. And, of course, not all vulnerable systems are effectively protected by firewalls.
This situation is so dire that I’ve included more information in the paid version of this week’s newsletter; but if you don’t get that version, you should just go directly to Microsoft bulletin
MS03-026 and download patches for your affected PCs. (Microsoft revised this bulletin as recently as July 21, so you should re-visit the document if you originally read it before that date.)
I haven’t learned of any negative side-effects of installing the patches, and in any event they would pale in comparison to the threat of your vulnerable machines remaining unpatched. If unexpected gotchas do arise, I’ll alert you in a future Brian’s Buzz. To send me more information about this, or to send me a tip on any other subject, visit
WindowsSecrets.com/contact.