UAC Whitelist Hole In Windows 7

David Gerard writes "Microsoft tried to make Vista secure with User Access Control (UAC). They relaxed it a bit in Windows 7 because it was such a pain in the backside. Unfortunately, one way they did this (the third way so far found around UAC in Windows 7) was to give certain Microsoft files the power to just ... bypass UAC. Even more unfortunately, one of the DLLs they whitelisted was RUNDLL32.EXE. The exploit is simply to copy (or inject) part of its own code into the memory of another running process and then telling that target process to run the code, using standard, non-privileged APIs such as WriteProcessMemory and CreateRemoteThread. Ars Technica writes up the issue, proclaiming Windows 7 UAC 'a broken mess; mend it or end it.'"

Comments

Re:Mend it or end it?

[fat_mike]

Seriously, it is 2009, can we knock off the stupid M$.

Re:If it was easy--

[newcastlejon]

I never heard of that. All the cars I have owned either prevent you from locking the driver's door when it's open or unlock the door if you close it when it's locked. (I assume you might bypass this by holding the handle as you described) For myself, I'd simply suggest that you lock doors after you use them rather than during.