Hacker News new | ask | show | jobs
by twoodfin 4988 days ago
This isn't really an exploit, except insofar as a local user can cause a DoS for the system. Until there's a demonstration that arbitrary code can be invoked with elevated privileges, it's just a bug.
1 comments

Agreed. Raymond Chen refers to these types of problems as involving "being on the other side of this airtight hatchway": http://blogs.msdn.com/b/oldnewthing/archive/2010/05/11/10009...
That's not entirely true - non-privileged local users are not supposed to be able to bluescreen the system. Note that, e.g. Terminal Server exists.
You can cause a blue screen by trying to copy the device context of the screen to itself with BitBlt - a stupid thing to do but still causes a blue screen
Sounds interesting. Anyone else have evidence for Microsoft's policy of ignoring local DoS vulns?
That sounds like a video driver bug, though.
Most probably not universally true. Care to provide more information?
Actually, Chen implies that it would be a security bug if an unprivileged user could do it on her own:

"Enabling the kernel debugger requires administrative privileges, so it's not like unprivileged users can force a system halt on their own".