3 ms·
> An additional desktop will be created. For those not familiar with Windows internals here's the documentation for the desktop[1] object. In particular note
by magicalhippo 6y ago
> An additional desktop will be created.
For those not familiar with Windows internals here's the documentation for the desktop[1] object.
In particular note the following:
"Window messages can be sent only between processes that are on the same desktop. In addition, the hook procedure of a process running on a particular desktop can only receive messages intended for windows created in the same desktop.
...
During the user's session, the system switches to the Winlogon desktop when the user presses the CTRL+ALT+DEL key sequence, or when the User Account Control (UAC) dialog box is open.
The Winlogon desktop's security descriptor allows access to a very restricted set of accounts, including the LocalSystem account. Applications generally do not carry any of these accounts' SIDs in their tokens and therefore cannot access the Winlogon desktop or switch to a different desktop while the Winlogon desktop is active."
Thus the exploit program shouldn't be able to press "Yes" on the UAC dialog. It seems the paper mentions this as well, but I didn't have time to study the rest of the paper to see how they overcome this to do interesting stuff.
[1]: https://docs.microsoft.com/en-us/windows/win32/winstation/desktops https://docs.microsoft.com/en-us/windows/win32/winstation/de...
- MisterKeylogger 6y ago> Thus the exploit program shouldn't be able to press "Yes" on the UAC dialog. This is correct!