Windows local privilege escalation 0-day exploit for NT->Windows 8
h-online.com/security/news/item/Google-resear...Posted Jun 4, 2013, 9:29 PM UTC
Posted Jun 4, 2013, 9:29 PM UTC
More Google vs Microsoft rivalry...
After discovering a bug in the Windows kernel's EPATHOBJ::pprFlattenRec function, he wrote to the list: "I don't have much free time to work on silly Microsoft code"
Yet found enough time to find an exploit, either he's lieing, or he's lieing.
Also it said he didnt disclose the exploit to Microsoft, but Google (his employer) says they should give them 1 week (currently being exploited by other people) or 60 days (not currently exploited by other people) notice.
IMO he's an ass for releasing it without disclosing it and giving Microsoft time to patch it. Obviously it's Google sanctioned too as he's done this many times, against their own policy, so for bickering between the two companies it's the users who lose.
Has it hit metasploit yet?
Does anyone have the compiled version? I only see the source on http://seclists.org/
Ormandy might be smart and capable of finding security bugs but he is a complete nitwit when it comes to social smarts. I get his logic that this forces companies, like Microsoft to respond. However I believe it is immature and irresponsible to not at least Microsoft even a 72 hour notice. There are better ways of handling this and this isn't the best.
What makes 72 hours reasonable? Why not 4 months? 2 minutes? At least we know about it now.
Because getting companies like Microsoft aware and working on a patch without working exploits allows them a headstart.
Now a situation has developed where an exploit is in the wild, Microsoft is playing catchup and supporting admins hope that Microsoft can turn around with a good patch, have to patch quickly and hope in the meantime none is their users will get infected.
It may have been reckless for Microsoft not to catch this but the equally reckless to play eye for an eye in order to get "attention" by releasing this into the wild.
Its actually a complex issue. My point about reasonable disclosure stands... what is reasonable? Also if you disclose it to the company they can claim credit for finding it... or not even acknowledge that you had anything to do with it.
We discussed this topic for a long time in my computing and ethics class.
What is reasonable? Enough time for the company to actually write and test a patch. A few days is nothing, a few weeks or so should be sufficient for complex cases. Releasing an exploit into the wild is only ethical when the company has refused to develop a patch in a reasonable time, has directly told you to get lost, or it is a feature that can safely and easily be disabled by admins.
I have also never heard a case of a company stealing credit for finding an exploit, especially as it is easy to document this stuff if you want to. Also, the security researchers ego should not even be a consideration here. If you release a 0-day because you are afraid of not getting credit then you are not a white-hat and are probably well on the way to being a black-hat.