A security feature in the 64-bit version of Windows Vista can be easily circumvented with a free utility that loads unsigned drivers into the kernel, according to researchers at Symantec.

Among 64-bit Vista's security provisions is one new to Microsoft's operating systems: only digitally-signed code can be loaded into the kernel. Under those new rules, code destined for the kernel -- typically drivers -- must be accompanied by a signed certificate available from a limited number of issuing authorities. Drivers not equipped with a legitimate certificate aren't loaded.

The thinking behind the move was that it would stymie rootkits, which load driver code into the kernel as part of their cloaking tactics.

But a pair of Symantec security researchers pointed to a free utility from Australian developer LinchpinLabs as one easy end-around. LinchpinLabs' Atsiv, said Ollie Whitehouse, an architect with Symantec's advanced threats research team, uses signed drivers to load other, unsigned code, into the Vista kernel.

"[Atsiv's] command line tool loads [its own] appropriate driver, which then in turn allows loading of unsigned drivers due to the implementation of their PE loader," said Whitehouse. "A side effect of using their own load is noted by the authors in their design documentation: 'Atsiv doesn't add the driver to the PsLoadedModuleslist so it is not visible in the standard drivers list.'

"This is rootkit-type behavior," said Whitehouse.

One of LinchpinLabs' developers, identified only as "Dan," argued on rootkit.com that Vista's signing requirement "doesn't prevent malware, it just prohibits freedom to choose." Dan also claimed that Microsoft could never prevent hackers from obtaining legitimate certificates.

"A signed file uniquely identifies the company that developed that file, but when companies can be created and registered in jurisdictions known for protecting the privacy of company founders and directors you have to ask what does driver signing actually represent?" Dan asked. "While driver signing certificates can be revoked, new certificates, with enough money, can be created faster than it takes to change a file's signature. If this is indeed the case, then it is the hobbyists and home user that end up paying the cost."

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.