The Curious Case of QueueUserAPC
specterops.io | blog
Summary
Summary Due to the nature of the .NET compiled language runtime, user asynchronous procedure calls (APCs) are processed upon the exit of any .NET assembly without manually triggering an alertable state from managed code. Further, if a user spawns a new process and queues an APC into the process’s main thread, a race condition exists […]
- Published
- Collected
--- id: 9833 title: "The Curious Case of QueueUserAPC" source_domain: specterops.io source_url: "https://specterops.io/blog/2019/07/01/the-curious-case-of-queueuserapc/" published_at: "2019-07-01T15:36:00Z" phying_url: "https://phying.com/item/9833" lang: en --- # The Curious Case of QueueUserAPC ## Summary Summary Due to the nature of the .NET compiled language runtime, user asynchronous procedure calls (APCs) are processed upon the exit of any .NET assembly without manually triggering an alertable state from managed code. Further, if a user spawns a new process and queues an APC into the process’s main thread, a race condition exists […] ## Intelligence Metadata - **Sources:** specterops.io - **Published:** 2019-07-01T15:36:00Z - **Original:** https://specterops.io/blog/2019/07/01/the-curious-case-of-queueuserapc/ - **Phying News:** https://phying.com/item/9833