I have a DLL that I inject into another process but I want to be able to call the exports on that DLL from my application. I've read elsewhere that you have to the SendMessage API but I have no idea what to do. Is there any example code on how this is done?
While it is not possible to directly call a function in another process, you can do it indirectly pretty easily with a few steps and the Windows API.
LoadLibrary
and GetProcAddress
from your own process. kernel32.dll
should be loaded at the same address in every process, so you can rely on them being present in the process into which you are injectingstruct
that will hold all the arguments you want to pass to your function that will call the functions in the other process (because CreateRemoteThread
can only pass one argument to a function, so we'll use it to pass a pointer to the structure) which at least contains member function pointers to hold the addresses of LoadLibrary
and GetProcAddress
VirtualAllocEx
, then fill it with the correct information with WriteProcessMemory
struct
you wrote, that uses LoadLibrary
/GetProcAddress
to call the function you want. Remember to use the pointers to those functions in the struct you are passing the function, not the names.VirtualAllocEx
, making sure to pass VAX
the PAGE_EXECUTE_READWRITE
flag so that it can hold executable codeRead/WriteProcessMemory
VirtualAllocEx
) by using CreateRemoteThread
.Make sure that all the data you pass to the function is either stored inside the struct and/or resides in the remote process's address space (get it there with VirtualAllocEx
/WriteProcessMemory
.
It may look a little involved, but it's not really that complicated. If you need some help with it, feel free to ask in a comment.
You can't directly call functions in another process, in general. There are, however, some workarounds you can use.
First, if you know the address of the export (which isn't the case a lot of the time), and the function you call uses the __stdcall
calling convention, takes a pointer-sized integer as an argument, and returns a DWORD, you can use CreateRemoteThread
to execute it in a thread in the remote process. This is often used to run LoadLibrary
to inject a DLL into a target process, since LoadLibrary
is loaded in the same address on all processes on a given computer.
Otherwise, the DLL you inject will need to do some sort of RPC with the process that called it. For example, you could have your injected DLL spawn a thread in its DLL_PROCESS_ATTACH handler, which in turn connects to a named pipe, or connects over COM or something to the master process.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With