Yesterday we reported on a major UAC security flaw where malicious hackers could potentially execute a script on a users machine by tricking into them into opening a disguised exe. This script would disable UAC without user interaction and without the users knowledge.A Microsoft spokesperson has provided Neowin with a response to the issue:
- This is not a vulnerability. The intent of the default configuration of UAC is that users don't get prompted when making changes to Windows settings. This includes changing the UAC prompting level.
- Microsoft has received a great deal of usability feedback on UAC prompting behavior in UAC, and has made changes in accordance with user feedback.
- UAC is a feature designed to enable users to run software at user (non-admin) rights, something we refer to as Standard User. Running software as standard user improves security reduces TCO.
- The only way this could be changed without the user's knowledge is by malicious code already running on the box.
- In order for malicious code to have gotten on to the box, something else has already been breached (or the user has explicitly consented)
















Since UAC is supposed to be so great, then any changes to it should prompt for action. The registry run keys and winlogon should be other areas that's watched and reported on, IMO.
UAC is not useless, users bitching and moaning about it and wanting it gone or less effective are the useless ones.
And I don't think it changes the registry, in this case it's faking user input to change it through the control panel. I could be wrong but the registry should still be covered the same was it is in vista since users don't normaly go poking around and changing things in there.
And I don't think it changes the registry, in this case it's faking user input to change it through the control panel. I could be wrong but the registry should still be covered the same was it is in vista since users don't normaly go poking around and changing things in there.
Personally,
I not only think it's useless and stupid, it's a MAJOR PITA!!
Have to give MS credit though. They've helped me make several hundred dollars by other people trying to disable it and not knowing what they're doing, and then me fixing their stuff.
I don't get this double standard that's set.
I don't get this double standard that's set.
Allow me to repeat what you're saying.
I don't get this double standard that's set.
exactly. apparently its annoying and useless to click a button but on linux and osx its ok to type a long password everytime you want to do something.
I don't get this double standard that's set.
exactly. apparently its annoying and useless to click a button but on linux and osx its ok to type a long password everytime you want to do something.
So true...
I don't get this double standard that's set.
exactly. apparently its annoying and useless to click a button but on linux and osx its ok to type a long password everytime you want to do something.
So true...
Your typical windows user (as we know) is an idiot and cant be trusted with ****. On the other hand, your typical linux user an uber geek and some what with OS X.
So yeah you think the security would be the other way around. Or not! Geeks care more about security!!
I agree with this to a certain point. Even though the system is already compromised, UAC could still be another barrier for malware. Does system center notify the user that UAC is disabled?
Also, as it is stated by MS, for this to work something else has already gotten into your system. UAC isn't useless at all, saying so is stupid. IF something already got into your system, then on any OS not just Win7 or Vista, it'll then find a way to do something else.
The key here is to stop the initial breach, if users can't stop that then anything else isn't going to help much.
And what happens in the default quiet state of UAC when something pokes in to the registry and turn it and action center off?
So this is why UAC is useless right now...
UAC is pro-active unless you make it not be by setting it low or off. The fact you even have the choice in Win7 compared to Vista is because USERS ASKED FOR IT.
Yet people moan that MS doesn't listen to them. We'll here is a case in point where they have.
Now its not as safe and you still complain.
You get what you deserve.
Now its not as safe and you still complain.
You get what you deserve.
LOL.
This would be fixed if MS simply put a single warning on changing UAC permission levels. Something that should be blatantly obvious since it's a SECURITY feature. That wouldn't change the overall "feel" of Windows 7's reduced nagging. It would only be a single more dialog box in the specific case of changing UAC settings, which a user normally never do.
But Microsoft doesn't want to, because they're idiots.
I, for one, am going to keep it at the highest level, which is Vista UAC.
This is the default level in Windows 7. Can you see the potential for ugly malware now?
UAC off by default for me
Now if you want it off, that's your choice, more power to you, but if you get bit in the but later don't turn around and moan that Windows isn't secure when you turn off one of the security features yourself.
Now if you want it off, that's your choice, more power to you, but if you get bit in the but later don't turn around and moan that Windows isn't secure when you turn off one of the security features yourself.
I agree with this. It's like saying your anti-virus software is useless after you've turned it off.
Now if you want it off, that's your choice, more power to you, but if you get bit in the but later don't turn around and moan that Windows isn't secure when you turn off one of the security features yourself.
I agree with this. It's like saying your anti-virus software is useless after you've turned it off.
It should only prompt you when you run the program, not every time it runs its check.
So the utility runs a check every x minutes and prompts you if it found any changes. Using it for years and never had any malware/rootkit.
Ain't gonna turn it off to please uac. Just add to UAC a whitelist and then it's somewhat useful, because being warned by UAC that my registry protection works every time is pretty annoying
Last edited by petrossa on 31 Jan 2009 - 11:36
So the utility runs a check every x minutes and prompts you if it found any changes. Using it for years and never had any malware/rootkit.
Ain't gonna turn it off to please uac. Just add to UAC a whitelist and then it's somewhat useful
Why don't you just use something like teatimer that comes with spybot, that just tells you when a registry setting has been changed instead of checking every 10 minutes whether you've been using the computer or not?
Wait, you paid for that software? Yipes..
It warns that an application needs elevation. Just the regular. And as i said before, with Vista it passes without elevation prompt.
It just sounds like it's doing something that is different for Win7 compared to Vista.
It just sounds like it's doing something that is different for Win7 compared to Vista.
A 'registry tracer' would be utterly useless against a rootkit. A rootkit hides itself from the registry at the kernel level.
Few people go in and tinker with their system settings every day.
Few people go in and tinker with their system settings every day.
As a developer I get prompted several times a day, but that is to be expected
And do they actually need them? I take it a few will if they do low-level stuff, but like you said, that's expected.
The same would happen under any other OS with their own version of UAC, unless you ran as root/admin.
And yes. They should also require a Secure Desktop prompt when changing UAC settings.
Amen to that
There are already multiple prompts and warnings when running anything downloaded from the Internet - one more isn't going to stop people who are determined to install something. Really, the virtualization for low-rights users and IE Protected Mode are the only useful parts of UAC. I'd love to see it taken one step farther and have "Continue, Cancel, Virtualize" in the UAC dialog (essentially an integrated Sandboxie), but I can see that confusing a *ton* of people.
Exactly, MS has left us with a "choice". No fault to MS if we don't exercise that choice. In my daily work, mainly using Word and some translation related programs I get few if any UAC prompts (at high).
Maybe they just don't know how to fix it.
See?
See?
You're absolutely right and that's the point - they're in a kind of dramatic situation
The thing is, malware running even with standard user privileges is plenty bad. It can still add itself to run at start-up (for that user), and can still read / write / delete data in any locations that user can access.
So the most important boundary is the Low IL -> Medium IL one, used by IE in Protected Mode and some other processes, which is still protected just as much as in Vista (or moreso) in this default state.
See?
You're absolutely right and that's the point - they're in a kind of dramatic situation
I don't see how. All it would require is a single prompt added whenever changing UAC settings. That doesn't mean making it exactly like Vista UAC in all cases.
That wouldn't really achieve anything. In anything less than the "high" UAC setting, any medium IL app can trivially elevate itself to high IL.
The lower settings largely exist to keep IE's protected mode and other Low IL isolation mechanisms in place, while being more "user friendly." They also still run most applications with reduced privileges, so code injection into those processes (like, say, Outlook or Firefo
But yeah, if this mode were as secure as the "high" mode there wouldn't be a "high" mode.
See?
No, I don't see. They could retain the standard Windows 7 UAC setting here, just apply an extra nag for changing the UAC level. Nothing more, and still faaar less nags than in Vista. Most user wouldn't even notice the difference, because people generally don't meddle with the UAC setting.
See?
Anybody can set the UAC slider to whatever they feel comfortable with.
The slider should be cranked up to max by default.
No matter where the slider is, there should be a secure UAC prompt to move it.
done.
Then it should be made possible, or at least, when a UAC change is registered, a prompt should be displayed.
I agree. The registry setting for UAC, as well as the run keys and winlogon should have higher protections. If those are accessed for any reason, either thru changing them at UI level, or directly poking around in the registry, there should be some alert that they are being changed.
Don't want UAC, switch it off but attain to the consequences and make sure you're a safe browser on the web. That means also scanning anything you download of a torrent these days, plenty trojans get in for free, good luck!
That's exactly what people here (at least the intelligent ones who aren't Microsoft apologists) are asking for, but so far Microsoft is refusing to do that.
Circumvent the elevation dialog? Are you saying applications can already elevate themselves without prompting? Then what use is UAC to begin with?
See my post above. It provides a mechanism for running processes in the "low" integrity level, such as Protected Mode IE and others. The is a HUGE security benefit.
It's really quite simple. If you are concerned about the boundary between medium IL (normal apps) and high IL (admin apps), which is arguably of small benefit especially on single-user systems, then use the "high" UAC setting. That's what it's there for.
The "Secure Desktop" mode which is in Vista can't be fooled, so no app can change the UAC because no app can gain mouse or keyboard access or any other sort of access to any input device in the secure desktop mode, that was why MS did it, and in my post I said "the secure desktop mode shows" to prompt user of he want to change the UAC behavior.
Clippy? It's a Feature.
UAC? Also a Feature.
BSOD? Merely a blue Feature.
See? With a feature-packed lineup like that, it's no Microsoft products are so popular.
worth trolling? no.
worth trolling? no.
+1
Wow, talk about being uninformed.
1. UAC doesn't ask you multiple times to do one thing.
2. Desktop is not a protected location, so UAC prompts from there are impossible.
Get your facts straight, computergeek. Your username doesn't suit you since you know nothing about them.
1. UAC doesn't ask you multiple times to do one thing.
2. Desktop is not a protected location, so UAC prompts from there are impossible.
Get your facts straight, computergeek. Your username doesn't suit you since you know nothing about them.
It sounds like you're also uninformed. You can get a UAC prompt deleting something from your desktop. Your visible desktop is actually two folders merged into one. The All Users desktop (at C:Documents and SettingsAll UsersDesktop or C:UsersPublicDesktop) and your own personal desktop (C:Documents and Settings\Desktop or C:Users\Desktop). If you try to delete something from *your* desktop you don't get prompted. If you try to delete something from the *all users* desktop which is a *system wide* desktop you will get prompted since it will affect all users on the machine.
must be tough for you.
well, he did say "his" desktop. If he's a computer geek, then surely he'd get the concept of the merged desktops that you explained (correctly & succinctly to your credit).
1. UAC doesn't ask you multiple times to do one thing.
2. Desktop is not a protected location, so UAC prompts from there are impossible.
Get your facts straight, computergeek. Your username doesn't suit you since you know nothing about them.
It sounds like you're also uninformed. You can get a UAC prompt deleting something from your desktop. Your visible desktop is actually two folders merged into one. The All Users desktop (at C
The public desktop folder is also not a protected folder.
::sigh::
It may be obvious, but it is FAR FAR from a simple fix. Clearly, if there was a simple fix - it would have been impleneted. You try writing code that can tell the difference from a human changing the control panel setting vs an automated script. Its is incredibly difficult, if not boderline impossible.
No, it actually IS a simple fix; in Windows Vista, launching any process gives the developer the opportunity to ask for permission elevation. The reason Microsoft doesn't do this is not due to difficulty, but because of a mismatch in their odd Windows 7 design docs.
So what's the big deal? It's been this way for 3+ years now, since the early betas of Vista. Get over it!!
Thus this article is nothing but fear mongering and utter BS!!
As Microsoft has stated many times, this is not a security flaw but simply a limitation (by design since users requested it to be this way mind you).
Seems some neowin staff is out get Microsoft once again!!! Epic failure!!
Read:
http://blogs.msdn.com/crispincowan/archive...-floor-wax.aspx
http://technet.microsoft.com/en-us/magazine/2007.06.uac.aspx
http://blogs.technet.com/markrussinovich/a.../12/638372.aspx
Last edited by war on 01 Feb 2009 - 00:48
And I love it even more when those same people don't have a clue about the technology involved.
And I very much love it when people like yourself spread this FUD knowing full well they don't have a clue. Even more when they write for a site as big as neowin!
You really should read http://blogs.msdn.com/crispincowan/archive...-floor-wax.aspx again.
I quote:
"Clearly, all security boundaries are security features, but not all security features are security boundaries."
"Security Boundary: this is a special term to Microsoft. It means that if someone discloses a way to violate a Microsoft-defined security boundary, that Microsoft will release a security patch as soon as possible, so that the method to violate the boundary no longer works against patched systems."
From Mark I quote:
"It should be clear then, that neither UAC elevations nor Protected Mode IE define new Windows security boundaries.
Microsoft has been communicating this but I want to make sure that the point is clearly heard. Further, as Jim Allchin pointed out in his blog post Security Features vs Convenience, Vista makes tradeoffs between security and convenience, and both UAC and Protected Mode IE have design choices that required paths to be opened in the IL wall for application compatibility and ease of use."
I quote again:
"Because elevations and ILs don’t define a security boundary, potential avenues of attack , regardless of ease or scope, are not security bugs."
So again Sir, I say to you, that this article is total BS and needs to be redacted! Seems you need an editor!! Damn I love the media, always ****ing it up for the little guy!!
At the very least, the last "paragraph" should be removed and neowin and yourself should offer both Microsoft and all Neowin visitors an apology for blowing this way out of context and for misleading your users..
Last edited by war on 01 Feb 2009 - 04:30
I feel that rather than do nothing microsoft must act right now and make the changing of the UAC something where it needs a PASSWORD.
Everthing else no password required but changing definitely !!!!
The current settings are fine. If you want to protect the normal -> admin boundary, use the "high" setting. That's what it is there for.
# In order for malicious code to have gotten on to the box, something else has already been breached (or the user has explicitly consented)
You need the damn UAC setting prompt so you are ALERTED TO THE FACT THAT THIS HAS HAPPENED SOMEHOW ASAP.
Yes the user may have done something stupid to allow infection, but the UAC setting prompt would then protect them from further damage even before the malicious code check package was updated to find whatever was out there infecting systems.
Microsoft's two last points there are moot because UAC was intended to protect the user from him/herself. Read "trojans".
Last edited by Jugalator on 01 Feb 2009 - 23:01
I guess when people keep changing what they actually want and Microsoft keeps trying to deliver they just can't win.
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.