This Blog

Syndication

Get Connected With Aubrey

Massive Security Hole In Windows 7

User Account Control in Vista was a really good idea that was pretty poorly implemented. In fact it’s downright annoying at times. Microsoft has decided to tweak it in Windows 7 and make it a little more user friendly, and they have done a pretty good job of that. There are now four levels of UAC, so you can adjust what will dim your screen and ask for a confirmation, and basic things like “Show processes from all users” in Task Manager no longer require confirmation at all.

However, Microsoft has overlooked something very basic that amounts to a huge security risk. Turning UAC off does not cause any sort of a prompt. This means that malware will be able to programmatically disable UAC without a user’s knowledge. Once that happens, the malware will pretty much be free to operate with full admin rights, and the user will be none the wiser.

In my opinion, that is even worse than not having UAC to begin with. If a user thinks they have UAC protecting them, but it has been disabled, they may unwittingly run any number of malicious items thinking that UAC is keeping them safe. Microsoft really needs to fix this if they’re the least bit concerned about security.

UPDATE: Yes, Microsoft has thought of this, they’ve been told about it repeatedly, but they still intend on releasing it this way. And as for it being something that can’t be done programmatically, check out Long’s post where you can download some code that will do it for you.

Only published comments... Jan 29 2009, 05:27 PM by Aubrey

Comments

 

Nicholas said:

You could also turn off UAC in Windows Vista. Ultimately it is up to the user to turn it of the same way it is not to install an anti-virus. Microsoft will recommend leaving it on, but ultimately it's the user's choice.

January 29, 2009 6:15 PM
 

Fowl said:

I can't belive they haven't come up with some sort of mitigation for this - this was the one of the main arguments for the design of UAC in Vista. They wouldn't have just "given up".

January 29, 2009 6:52 PM
 

Moh said:

Seriously it can be a  massive one... I havn't gone through documentations but maybe it is an option that cannot be changed programatically... Like Turning off System Restore...

January 29, 2009 6:54 PM
 

The Dave said:

There is no prompt only when you already have UAC set to "Don't notify me when I make changes to Windows settings"

This makes sense, this option all but completely neuters UAC anyway.  With this mode set it's possible to install drivers, create new tasks with the "Run with higher privileges" and perform various other tasks that would ultimately allow user defined scripts or code to run.

The vulnerability here is allowing anything, absolutely anything anywhere, to run with administrative rights without a UAC prompt first.

January 29, 2009 8:13 PM
 

Tom said:

Holy crap, do you HONESTLY think they haven't thought of this?

Claiming they haven't is almost as bad as claiming you'd do a better job!

January 29, 2009 10:32 PM
 

dugbug said:

"Turning UAC off does not cause any sort of a prompt"

Are you saying that changing the SETTING of UAC to off (when UAC is enabled) is accepted by windows without any prompting?  Or that once you turn UAC off you see no prompts for system changes (which I would expect)?

January 30, 2009 6:02 AM
 

Sebastian said:

dugbug,

Disabling the UAC does not require a prompt. Once it's disabled, nothing requires a prompt.

January 30, 2009 8:29 AM
 

The Dave said:

Turned off UAC requires a prompt if UAC was fully enabled.  This is secure.

Turning off UAC doesn't require a prompt if UAC was already set to "don't prompt when Windows asks".  This isn't secure, but this setting is already unsecure in so many ways that being able to turn UAC off completely doesn't even make the list.

January 30, 2009 9:24 AM
 

Jeroen said:

How about putting the UAC control panel applet on the secure desktop, just like CardSpace? That should stop this hack very easy!

January 30, 2009 10:01 AM
 

Anonymous said:

For crying out loud: ditch UAC and stop running as admin! It's so bl**d1 simple...

January 30, 2009 6:13 PM
 

Corrine said:

I pointed Bill Pytlovany to your blog post, Aubrey.  His response:  

"WinPatrol v16 wlll include a feature that lets you know if your UAC settings have changed."

twitter.com/.../1163371356

WinPatrol v16 Beta has been working splendidly on Windows 7.  This new feature will be yet another plus.

January 30, 2009 6:24 PM
 

Aubrey said:

While I'm glad that WinPatrol will let you know if your UAC settings change, the fact that Microsoft is going to ship Windows 7 with UAC at a level by default that will allow it to be turned off without any notification is still a huge problem. They really need to address this before RTM.

January 30, 2009 10:23 PM
 

Gaurav said:

I checked the post, and i also think it is very SERIOUS ISSUE, and i don't think, it is difficult for MICROSOFT to change this thing, so that whenever UAC settings are changed, it must be notified to the USER.

Really a serious issue !!!!!!!!!!!

January 31, 2009 1:21 AM
 

Ian said:

The issue seems to be gaining more momentum, so I'm sure something is going to change between now and release.

February 1, 2009 3:38 AM
 

Cutie said:

Security is important and necessary. M$ has simply been doing it the wrong way and trying to satisfy all while ending up enraging all.

The whole idea of UAC is flawed to begin with and should be useful only to savvy administrators. A major issue with UAC is that it unloads all the security burdens to the user, who would probably not have the time/effort and security savvy to interpret all the messages and decide quickly at the spot. Secure configuration is necessary, and user-friendly warnings are desirable. But for an average user M$ shall at least provide sufficient defaults for access control, and its UI designers shall not have made the user-friendly messages confusing and meaningless.

I'd say, the best bet is rule-based access control with an adequate set of default settings (5 levels is probably enough). That way, the user can decide or even define which actions should cause warnings and UAC confirmation and which ones would not. And if the user doesn't even know what those actions are, then they should not touch the rules.

February 3, 2009 9:52 AM
Thanks for sharing your feedback! If your feedback doesn't appear right away, please be patient as it may take a few minutes to publish - or longer if the blogger is moderating comments.
Windows is a registered trademark of Microsoft Corporation.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems Themed By nb development