For Microsoft, delivering high-quality security patches in a timely manner has always been a lose-lose predicament.
If patches for major software vulnerabilities take too long, customers are at the mercy of zero-day threats. When patches are rushed out without proper quality assurance testing, they invariably become a system administrators worst nightmare.
Earlier this week, when Microsoft Corp. announced plans to re-release a "critical" bulletin because of patch quality problems, the move triggered a new round of eye-rolling among security research pros.
The bulletin, MS05-019, first released in April, contains patches that have caused major connectivity problems for network administrators.
The connectivity errors range from the inability of Exchange servers to talk to their domain controllers; failure of domain controller replication across WAN (wide area network) links; and inability to connect to terminal servers or to file share access.
Microsoft also acknowledged that networking programs that send TCP packets or UDP packets over raw IP sockets "may stop working" after the security update is applied on a computer running Windows XP SP1 (Service Pack 1).
A knowledge base article has been posted to highlight the problems, and hotfixes have been offered to provide temporary respite, but despite Microsofts insistence that the problems affect only a small number of customers, security experts said the re-release of a high-severity bulletin points to a weakness in Microsofts patch creation process.
"A hotfix for a patch? I hope it works properly, or whats next? A hotmend for the hotfix for the patch?" asked Corey Nachreiner, a network security analyst at WatchGuard Technologies Inc.
In an interview with Ziff Davis Internet News, Nachreiner said some of his companys clients have complained that the patches have broken VPN connections, a problem he described as "a big deal" for the SMB (small and medium-sized business) market segment.
Because the patch is rated critical by Microsoft, Nachreiner said he cannot recommend uninstalling the patch.
"It means that a lot of customers are scrambling to get hotfixes to keep their systems connected."
Officials at Microsoft insisted the company is doing "far more for this one than necessary" to help ensure every customer has the most recent changes to the update.
"The problem being addressed is only present when a customer has specific MTU settings on their routers on their network, and is very rare," a spokeswoman said.
"Due to the variation in network configurations made possible by third-party routers and TCP/IP devices, this is not a scenario that can be tested internally at Microsoft. The MSRC [Microsoft Security Response Center] is taking this additional step because of the feedback received from customers," she added, insisting that the pool of customers affected by this issue is quite small.
However, as WatchGuards Nachreiner points out, a small pool of Microsofts massive user base is still a very significant number.
"When we are dealing with Microsoft updates, one thing we always reiterate, then reiterate some more, is to test before deploying. The guidance is always to download, test, then deploy the patches. With Microsoft, the test section of our guidance has gotten larger and larger."