3 ms·
This doesn't seem all that exciting to me. If you have a handle to a target thread that allows you to call QueueUserAPC, it's game over already. You can own t
by amluto 10y ago
This doesn't seem all that exciting to me. If you have a handle to a target thread that allows you to call QueueUserAPC, it's game over already. You can own that thread in so many ways that I don't see why a new one is exciting. (Heck, you could just use the debugging APIs.)
This seems like of like saying "hey look, root on a Linux system can inject code into Chrome". No kidding.
- userbinator 10y agoIndeed, the basic mindset and operating premise of these security companies is to find anything that could even be the tiniest bit exploitable and hype it as a huge risk... I have a suspicion that they will not be satisfied until everyone's computers are turned into virtual prisons and controlled by some central entity.
- TheDong 10y agoAnd no one can add a new bit of software to this computer you "own" until the software has submitted to draconian laws and been reviewed by their experts who will entirely decide your developer livelihood. You'll pay money for the possibility to maybe let a user ever run the software you spent years developing. We'll call it the iPhone.
- 13of40 10y agoI think the point is that contemporary malware detection closely monitors straightforward APIs like CreateRemoteThread, but this technique flies below the radar for now. It's just another iteration of the arms race.
- Const-me 10y agoThat was true 15 years ago, when people run Windows XP using an Administrator account. Those years, without a third-party security product monitoring various API calls, you were pretty much screwed. In modern Windows however, UAC has largely managed the attack vector. Here’s more details on this particular issue: https://blogs.msdn.microsoft.com/oldnewthing/20150519-00/?p=45571 https://blogs.msdn.microsoft.com/oldnewthing/20150519-00/?p=...