Revision as of 21:49, 6 September 2018 edit 2001:4898:80e8:a:c6e:5343:3e58:c3e9 (talk) Undid revision 857036494 by Guy Harris (talk) The bug is not in ALPC but rather in how the particular server service operates Tags: Undo references removed ← Previous edit		Revision as of 21:51, 6 September 2018 edit undo 2001:4898:80e8:a:c6e:5343:3e58:c3e9 (talk) Undid revision 857035165 by 109.252.52.37 (talk) The bug is not in ALPC but rather in how the particular server service operates) Tags: Undo section blanking Next edit →
Line 29: As mentioned, Microsoft RPC can use (A)LPC as a transport when the client and server are both on the same machine. Many services that are designed to communicate only on the local computer use (A)LPC as the only transport through RPC. The implementation of remote [[object linking and embedding\|OLE]] and [[Distributed Component Object Model\|DCOM]] in many cases uses (A)LPC for local communication as well. ~~==Bugs==~~ As of 28.08.2018, a programmer named SandboxEscaper [https://www.bleepingcomputer.com/news/security/exploit-published-for-unpatched-flaw-in-windows-task-scheduler/ released] a Proof-of-Concept code that exploits a bug in (A)LPC interface of Task Scheduler component in Windows 10 allowing a local attacker to gain local system privileges. ==See also==

Local Inter-Process Communication: Difference between revisions