After CERT warning, Microsoft delivers AutoRun fix

[dhilipkumar]

After CERT warning, Microsoft delivers AutoRun fix


Microsoft is pushing out a software update to some Windows users that fixes a bug in the Windows AutoRun software, used to automatically launch programs when DVDs or USB devices are introduced to the PC.

The bug fix, delivered through Microsoft's standard automatic update systems, comes one month after the U.S. Computer Emergency Readiness Team (US-CERT) issued a security alert warning that Windows did not properly disable AutoRun on Windows 2000, XP and Server 2003.

"Disabling AutoRun on Microsoft Windows systems can help prevent the spread of malicious code," CERT said in its advisory. "However, Microsoft's guidelines for disabling AutoRun are not fully effective, which could be considered a vulnerability."

Microsoft had said that technical users could disable AutoRun by setting a Windows Registry value called NoDriveTypeAutoRun to 0xFF. The problem was that, even with this value set, some versions of Windows would launch AutoRun programs whenever the user clicked on a device's icon using Windows Explorer.

That could mean big trouble for some users, as the widespread Conficker worm uses AutoRun to spread from USB devices to PCs.

There has been some internal debate within Microsoft as to whether Windows should enable AutoRun by default, since the software can be misused. AutoRun helped install the notorious Sony rootkit copy-protection software on users' PCs four years ago.

Although Microsoft describes its fix as a nonsecurity update, the patch "certainly does have security implications," said Ben Greenbaum, a senior research manager with Symantec Security Response. "It allows users who were expecting -- with good reason -- a certain level of protection out of the feature to actually get that level of protection."

It turns out that Microsoft had actually produced a patch for the issue, which users could download themselves, as far back as May 2008. It had also pushed out a July update that fixed the problem for Vista and Server 2008; but this fix was not automatically updated for Windows 2000, XP and Server 2003 users until Tuesday