我知道在stackoverflow上有几个类似的问题,但都没有解决我的问题。
所以我正在写一个c#框架,用于低级的进程间操作,包括一个dll注入功能。
在调用我的注入器之前,我已经通过使用 OpenProcess()
与 PROCESS_ALL_ACCESS
以下是我的注入器代码(我知道由于所有的调试打印,可读性受到很大影响)。
public void Inject(string dllName, bool printDebugInfo)
{
// Check if we are attached to the process.
target.Assertions.AssertProcessAttached();
target.Assertions.AssertInjectionPermissions();
// searching for the address of LoadLibraryA and storing it in a pointer
IntPtr kernel32Handle = WinAPI.GetModuleHandle("kernel32.dll");
if (kernel32Handle == IntPtr.Zero)
{
uint errorCode = WinAPI.GetLastError();
throw new Win32Exception((int)errorCode, "Encountered error " + errorCode.ToString() + " (0x" + errorCode.ToString("x") + ") - FATAL: Could not get handle of kernel32.dll: was NULL.");
}
UIntPtr loadLibraryAddr = WinAPI.GetProcAddress(kernel32Handle, "LoadLibraryA");
if (loadLibraryAddr == UIntPtr.Zero)
{
uint errorCode = WinAPI.GetLastError();
throw new Win32Exception((int)errorCode, "Encountered error " + errorCode.ToString() + " (0x" + errorCode.ToString("x") + ") - FATAL: Could not get address of LoadLibraryA: was NULL.");
}
HelperMethods.Debug("LoadLibraryA is at 0x" + loadLibraryAddr.ToUInt64().ToString("x"), printDebugInfo);
// alocating some memory on the target process - enough to store the name of the dll
// and storing its address in a pointer
uint size = (uint)((dllName.Length + 1) * Marshal.SizeOf(typeof(char)));
IntPtr allocMemAddress = WinAPI.VirtualAllocEx(target.Handle, IntPtr.Zero, size, (uint)Permissions.MemoryPermission.MEM_COMMIT | (uint)Permissions.MemoryPermission.MEM_RESERVE, (uint)Permissions.MemoryPermission.PAGE_READWRITE);
HelperMethods.Debug("Allocated memory at 0x" + allocMemAddress.ToInt64().ToString("x"), printDebugInfo);
int bytesWritten = 0;
// writing the name of the dll there
byte[] buffer = new byte[size];
byte[] bytes = Encoding.ASCII.GetBytes(dllName);
Array.Copy(bytes, 0, buffer, 0, bytes.Length);
buffer[buffer.Length - 1] = 0;
bool success = WinAPI.WriteProcessMemory((uint)target.Handle, allocMemAddress.ToInt64(), buffer, size, ref bytesWritten);
if (success)
{
HelperMethods.Debug("Successfully wrote \"" + dllName + "\" to 0x" + allocMemAddress.ToInt64().ToString("x"), printDebugInfo);
}
else
{
HelperMethods.Debug("FAILED to write dll name!", printDebugInfo);
}
// creating a thread that will call LoadLibraryA with allocMemAddress as argument
HelperMethods.Debug("Injecting dll ...", printDebugInfo);
IntPtr threadHandle = WinAPI.CreateRemoteThread(target.Handle, IntPtr.Zero, 0, loadLibraryAddr, allocMemAddress, 0, out IntPtr threadId);
HelperMethods.Debug("CreateRemoteThread returned the following handle: 0x" + threadHandle.ToInt32().ToString("x"), printDebugInfo);
uint errCode = WinAPI.GetLastError();
if (threadHandle == IntPtr.Zero)
{
throw new Win32Exception((int)errCode, "Encountered error " + errCode.ToString() + " (0x" + errCode.ToString("x") + ") - FATAL: CreateRemoteThread returned NULL pointer as handle.");
}
Console.WriteLine("CreateRemoteThread threw errorCode 0x" + errCode.ToString("x"));
Console.WriteLine("Currently the following modules are LOADED:");
ProcessModuleCollection processModules = target.Process.Modules;
foreach (ProcessModule module in processModules)
{
Console.WriteLine(" - " + module.FileName);
}
uint waitExitCode = WinAPI.WaitForSingleObject(threadHandle, 10 * 1000);
HelperMethods.Debug("Waiting for thread to exit ...", printDebugInfo);
HelperMethods.Debug("WaitForSingleObject returned 0x" + waitExitCode.ToString("x"), printDebugInfo);
Thread.Sleep(1000);
Console.WriteLine("Currently the following modules are LOADED:");
processModules = target.Process.Modules;
foreach (ProcessModule module in processModules)
{
Console.WriteLine(" - " + module.FileName);
}
success = WinAPI.GetExitCodeThread(threadHandle, out uint exitCode);
if (!success)
{
uint errorCode = WinAPI.GetLastError();
throw new Win32Exception((int)errorCode, "Encountered error " + errorCode.ToString() + " (0x" + errorCode.ToString("x") + ") - FATAL: Non-zero exit code of GetExitCodeThread.");
}
Console.WriteLine("Currently the following modules are LOADED:");
processModules = target.Process.Modules;
foreach (ProcessModule module in processModules)
{
Console.WriteLine(" - " + module.FileName);
}
HelperMethods.Debug("Remote thread returned 0x" + exitCode.ToString("x"), printDebugInfo);
success = WinAPI.CloseHandle(threadHandle);
if (!success)
{
uint errorCode = WinAPI.GetLastError();
throw new Win32Exception((int)errorCode, "Encountered error " + errorCode.ToString() + " (0x" + errorCode.ToString("x") + ") - FATAL: Failed calling CloseHandle on 0x" + threadHandle.ToInt64().ToString("x") + ".");
}
HelperMethods.Debug("Called CloseHandle on 0x" + threadHandle.ToInt64().ToString("x") + ".", printDebugInfo);
success = WinAPI.VirtualFreeEx(target.Handle, allocMemAddress, 0, 0x8000);
if (!success)
{
uint errorCode = WinAPI.GetLastError();
throw new Win32Exception((int)errorCode, "Encountered error " + errorCode.ToString() + " (0x" + errorCode.ToString("x") + ") - FATAL: Failed calling VirtualFreeEx on 0x" + allocMemAddress.ToInt64().ToString("x") + ".");
}
HelperMethods.Debug("Released all previously allocated resources!", printDebugInfo);
}
所有的WinAPI函数都是按照微软官方文档的规定被调用的(三番五次的检查)。
我调用我的代码如下
Target target = Target.CreateFromName("notepad++");
target.Attach(Permissions.ProcessPermission.PROCESS_ALL_ACCESS);
target.Injector.Inject(@"L:\Programming\C\test\newdll.dll",true);
的完整源代码。Target
课堂上 GitHub 但应该与这个问题无关。
这里最有趣的可能是 newdll.dll
用原生C语言编写,如下所示。
#include<Windows.h>
#include<stdbool.h>
__declspec(dllexport) bool WINAPI DllMain(HINSTANCE hInstDll, DWORD fdwReason, LPVOID lpvReserved)
{
switch (fdwReason)
{
case DLL_PROCESS_ATTACH:
{
break;
}
case DLL_PROCESS_DETACH:
{
break;
}
case DLL_THREAD_ATTACH:
{
break;
}
case DLL_THREAD_DETACH:
{
break;
}
}
return true;
}
这段代码显然没有什么作用 但由于从DllMain中产生类似于Messagebox的东西显然被认为是 "坏事",所以我就把它留在了这里。然而,如果注入是有效的,那么这个dll就会被列在 Process.Modules
(它不是)。
然而,当运行我的代码时,我从所有的调试打印中得到以下输出。
LoadLibraryA is at 0x778f60b0
Allocated memory at 0x9c0000
Successfully wrote "L:\Programming\C\test\newdll.dll" to 0x9c0000
Injecting dll ...
CreateRemoteThread returned the following handle: 0x22c
CreateRemoteThread threw errorCode 0x0
Currently the following modules are LOADED:
- J:\TOOLS\Notepad++\notepad++.exe
- C:\Windows\SYSTEM32\ntdll.dll
- C:\Windows\SYSTEM32\wow64.dll
- C:\Windows\SYSTEM32\wow64win.dll
- C:\Windows\SYSTEM32\wow64cpu.dll
Waiting for thread to exit ...
WaitForSingleObject returned 0x0
Currently the following modules are LOADED:
- J:\TOOLS\Notepad++\notepad++.exe
- C:\Windows\SYSTEM32\ntdll.dll
- C:\Windows\SYSTEM32\wow64.dll
- C:\Windows\SYSTEM32\wow64win.dll
- C:\Windows\SYSTEM32\wow64cpu.dll
Currently the following modules are LOADED:
- J:\TOOLS\Notepad++\notepad++.exe
- C:\Windows\SYSTEM32\ntdll.dll
- C:\Windows\SYSTEM32\wow64.dll
- C:\Windows\SYSTEM32\wow64win.dll
- C:\Windows\SYSTEM32\wow64cpu.dll
Remote thread returned 0x0
Called CloseHandle on 0x22c.
Released all previously allocated resources!
Press any key to continue . . .
可以看到,没有任何错误代码,也没有任何迹象表明 注入出了问题,除了... ... newdll.dll
从来没有被加载,因为它没有显示在加载模块中的 Process.Modules
.
那么我的代码有什么问题呢?
快速概述一下。我的确是按照以下程序来做的
OpenProcess()
与 PROCESS_ALL_ACCESS
GetModuleHandle("kernel32.dll")
GetProcAddress(kernel32Handle, "LoadLibraryA")
VirtualAllocEx(...)
和 WriteProcessMemory()
写下我的dll名称和路径。CreateRemoteThread()
加载dllWaitForSingleObject()
等待加载dll正如正确指出的那样,这种注入技术只有在从32位进程-->32位进程或从64位进程-->64位进程注入时才有效。我将我的代码编译成64位可执行文件,试图将我的dll注入到32位的notepad++.exe中。
另外,我还必须调整 WriteProcessMemory
调用,以符合32位内存空间的要求。所以从 bool success = WinAPI.WriteProcessMemory((uint)target.Handle, allocMemAddress.ToInt64(), buffer, size, ref bytesWritten);
到 bool success = WinAPI.WriteProcessMemory((uint)target.Handle, allocMemAddress.ToInt32(), buffer, size, ref bytesWritten);
做到了这一点。