said by Cartel:BTW with these updates:
An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.
So some "geek" sits at his computer and tries to sabotage it to find vulnerabilities and reports it to MS.
Well that's fine for a public library or the welfare office or some place you want restricted access, you would want to patch that so some clown can't mess everything up or use the computer for unscrupulous activities, but for me, nobody is getting near this computer unless its physically stolen then updates won't help you there.
No, these "must...be able to log on locally" "Elevation of Privilege" vulnerabilities are more important than you think! "Log on locally" could also be taken advantage of in the case of some exploit code that starts running in another process while browsing, etc.
Seems to me one of the most difficult things to protect against, and they are a major concern being on XP still next year after updates end. No new processes are created necessarily to notice or block, they just "elevate" using Windows system processes that are already there. Those, and the TrueType font-type vulnerabilities (fixed a few times now), which don't even require malicious code running first! Just the stupid way Windows handles font parsing in kernel mode. Kernel exploited and nothing you can do (so, I'd want to be
sure then to not let any browser, etc. use custom font files, however that can be set).