Microsoft changes Windows 7 UAC after new exploit code surfaces

Bug in User Account Control is now fixed, claims Microsoft, but not in beta version users have

A pair of Windows bloggers posted more proof-of-concept code today that subverts an important security feature of Windows 7, a problem that Microsoft knew about as long ago as last October and that one of its software engineers said would be fixed in the beta.

Today, however, the company said it had addressed the issue in post-beta builds that have not yet been released to the public.

According to bloggers Rafael Rivera and Long Zheng, hackers can easily piggyback on "preapproved" Microsoft applications and code to trick Windows 7 into granting their malicious code full access rights to a machine. "This is a real threat," Rivera, who is also a developer, said in an interview today. "No reconfiguration of UAC is necessary."

At issue is UAC, or User Account Control, a security feature that prompts users for their consent before allowing tasks such as program and device driver installation to take place. UAC, which debuted with Windows Vista in 2007, has been modified by Microsoft in Windows 7 in an attempt to dampen criticism of the feature, which has been blasted by users as being too intrusive.

In Windows 7, UAC prompts the user less frequently, in part because it checks to see whether the application making changes to the system is preapproved, said Rivera and fellow blogger Long. If the application is considered safe -- Microsoft uses a combination of a digital certificate and a new, undocumented flag to mark approved code -- UAC steps aside and "auto-elevates" the application without putting up a prompt.

The trouble, according to Rivera and Long, is that attackers can use one of several preapproved applications to fool Windows 7 into giving a malicious payload full administrative rights, something it would not have if the user were following Microsoft's advice and running the operating system in standard user mode.

"Windows will ... automatically elevate the process to High Mandatory Level, executing your payload wearing an administrative hat," Rivera said in a post to his blog early this morning.

The danger, he and Long argued, is real and significant. "Existing malware can be easily tweaked to accommodate the new weaknesses in Windows 7," Rivera said via instant messaging today.

Although Rivera and Long reported their concerns to Microsoft, it was not the first time the company faced questions over Windows 7's implementation of UAC. In late October, just days after Microsoft handed out an early version of the new operating system to developers at its Professional Developers Conference (PDC), users running the preview began debating UAC's weaknesses on Microsoft's own Channel 9 Web site.

In a message thread titled "Windows 7 UAC crippled -- I broke it already!" users criticized the changes Microsoft had made. "They're going way too far in the opposite direction now," said Sven Groot. "You might as well not have UAC at all and put up a sign 'malware welcome!' or something." That same day, Richard Turner, who identified himself as a software development engineer in Microsoft's Visual Studio group, defended UAC in Windows 7. He said the problems would be fixed before the company released a public beta.

1 2 Page
Join the discussion
Be the first to comment on this article. Our Commenting Policies