I don’t think “only invoke MSI signed executables” inspires confidence either. There’s ought to be an MSI signed executable that launches arbitrary executables by design and defeats the mitigation.
replyThe author got around a similar mitigation in their exploit for ASUS DriverHub (linked in the original article).
Oh right, yes, either that, or one of them is bound to have a DLL hijack issue that can be taken advantage of.
replyOr just a TOCTOU race :)
reply> At this point, just inject a thread into that GUI process and send the command
replyCan you or someone else expand on that?
Sure. On Windows, you can allocate memory into an arbitrary process’s address space with VirtualAllocEx, write arbitrary code into those allocated pages using WriteProcessMemory, and start a thread there with CreateRemoteThread.
replyNow, of course you can’t do this for every process, or it would be trivial to escalate privileges. But I’m pretty sure you can do this for child processes running as the same user.
Yep. There's a system of ACLs and integrity levels which determine whether you're allowed to do this or not (doesn't have to be a child process), but for the most common case:
reply* a process running at medium integrity level with the current user's token
* another medium integrity process with the same token can open it with PROCESS_CREATE_THREAD and PROCESS_VM_WRITE rights