一、unidbg 介绍
unidbg 是凯神 在 2019 年初开源的一个轻量级模拟器,一个基于Java的跨平台解密引擎,专门用于动态分析和逆向工程应用程序。它可以模拟不同CPU架构、操作系统和指令集,从而使用户能够在一个统一的环境中分析各种不同类型的二进制文件。unidbg的主要功能包括模拟执行、内存访问、指令跟踪、函数调用跟踪等。
unidbg 是建立在Unicorn引擎之上的,Unicorn引擎是一个强大的开源CPU模拟器框架,支持多种架构,包括x86、ARM、MIPS等,因此unidbg也能够模拟这些不同的CPU架构。UniDGB的另一个核心组成部分是Capstone引擎,它用于反汇编和指令解码。
unidbg 下载地址: https://github.com/zhkl0228/unidbg
二、框架快速搭建
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 | package com.kanxue.test2;import com.github.unidbg.AndroidEmulator;import com.github.unidbg.Module;import com.github.unidbg.arm.backend.DynarmicFactory;import com.github.unidbg.linux.android.AndroidEmulatorBuilder;import com.github.unidbg.linux.android.AndroidResolver;import com.github.unidbg.linux.android.dvm.AbstractJni;import com.github.unidbg.linux.android.dvm.DalvikModule;import com.github.unidbg.linux.android.dvm.VM;import com.github.unidbg.memory.Memory;import java.io.File;public class Test05 extends AbstractJni { private final AndroidEmulator emulator; private final VM vm; private final Module module; Test05(){ // 创建模拟器 emulator = AndroidEmulatorBuilder .for32Bit().addBackendFactory(new DynarmicFactory(true)) .setProcessName("cc.ccc.cc") .build(); // 内存调用 Memory memory = emulator.getMemory(); // 设定 SDK 版本 memory.setLibraryResolver(new AndroidResolver(23)); //创建虚拟机 vm = emulator.createDalvikVM(new File("sssss.apk")); //jni 日志打印 vm.setVerbose(true); // jni 设置 vm.setJni(this); // 执行so文件 DalvikModule dm = vm.loadLibrary(new File("ssss.so"), true); // 获取so 文件模块 module = dm.getModule(); //调用JNI——onload 函数 vm.callJNI_OnLoad(emulator,module); // dm.callJNI_OnLoad(module); }} |
三、基础文档
emulator 的操作
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | // 获取内存操作接口Memory memory1 = emulator.getMemory();// 获取进程idint pid = emulator.getPid();//创建虚拟机VM dalvikVM = emulator.createDalvikVM();//创建虚拟机并指定文件VM dalvikVM1 = emulator.createDalvikVM(new File("ss/ss/apk"));//获取已经创建的虚拟机VM dalvikVM2 = emulator.getDalvikVM();//显示当前寄存器的状态 可指定寄存器emulator.showRegs();// 获取后端CPUBackend backend = emulator.getBackend();//获取进程名String processName = emulator.getProcessName();// 获取寄存器RegisterContext context = emulator.getContext();//Trace 读取内存emulator.traceRead(1,0);// trace 写内存emulator.traceWrite(1,0);//trace 汇编emulator.traceCode(1,0);// 是否在运行boolean running = emulator.isRunning(); |
memory 操作
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | // 指定安卓sdk 版本 只支持 19 和 23memory.setLibraryResolver(new AndroidResolver(23));// 拿到一个指针 指向内存地址 通过该指针可操作内存UnidbgPointer pointer = memory.pointer(0x11111111);//获取当前内存映射的情况Collection<MemoryMap> memoryMap = memory1.getMemoryMap();//根据模块名 来拿某个模块Module sss = memory1.findModule("sss");// 根据地址 来拿某个模块Module moduleByAddress = memory1.findModuleByAddress(0x111111); |
VM 操作
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | //推荐指定apk 文件 unidbg会自动做许多固定的操作VM vvm = emulator.createDalvikVM(new File("ssss.apk"));// 是否输出jni 运行日志vvm.setVerbose(true);//加载so模块 参数二设置是否自动调用init函数DalvikModule dalvikModule = vvm.loadLibrary(new File("ss.so"), true);// 设置jni 交互接口 参数需要实现jni接口 推荐使用this 继承AbstractJnivvm.setJni(this);//获取JNIEnv 指针 可以作为参数传递Pointer jniEnv = vm.getJNIEnv();//获取JavaVM 指针Pointer javaVM = vm.getJavaVM();//调用jni_onload函数dalvikModule.callJNI_OnLoad(emulator);vm.callJNI_OnLoad(emulator,dalvikModule.getModule()); |
符号调用
1 2 3 4 5 6 7 8 9 10 11 | // 创建一个vm 对象,相当于 java 层去调用native函数类的实例对象// DvmObject obj = ProxyDvmObject.createObject(vm,this); // 默认获取MainActivity 当有很多类的时候,防止默认指定错误,可以以下指定DvmObject<?> obj = vm.resolveClass("com/example/demo01/MainActivity").newObject(null);String signSting = "123456";DvmObject dvmObject = obj.callJniMethodObject(emulator, "jniMd52([B)Ljava/lang/String;", signSting.getBytes(StandardCharsets.UTF_8));String result = (String) dvmObject.getValue();System.out.println("[symble] Call the so md5 function result is ==> " + result); |
地址调用
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | ArrayList<Object> args = new ArrayList<>();Pointer jniEnv = vm.getJNIEnv();DvmObject object1 = ProxyDvmObject.createObject(vm, this);// DvmObject<?> dvmObject = vm.resolveClass("com/xx/xx/MainActivity").newObject(null);args.add(jniEnv);// args.add(vm.addLocalObject(object1));// args.add(null) args.add(null);args.add(vm.addLocalObject(new StringObject(vm, "123456")));Number number = module.callFunction(emulator, 0x11AE8 + 1, args.toArray());// 是个地址System.out.println("[addr] number is ==> " + number.intValue());DvmObject<?> object = vm.getObject(number.intValue());System.out.println("[addr] Call the so md5 function result is ==> " + object.getValue()); |
参数 context
1 2 | DvmObject<?> context = vm.resolveClass("android/content/Context").newObject(null);list.add(vm.addLocalObject(context)); |
四、unidbg hook
hookZz
HookZz(Dobby)是一个轻量级、多平台、多架构的漏洞利用钩子框架。Unidbg中是HookZz和Dobby是两个独立的Hook库,因为作者认为HookZz在arm32上支持较好,Dobby在arm64上支持较好。HookZz是inline hook方案,因此可以Hook Sub_xxx,缺点是短函数可能出bug,受限于inline Hook 原理。文档看https://github.com/jmpews/HookZz
hookZz (1)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | IHookZz hookZz = HookZz.getInstance(emulator); // 加载HookZz,支持inline hookhookZz.enable_arm_arm64_b_branch(); // 测试enable_arm_arm64_b_branch,可有可无hookZz.wrap(module.findSymbolByName("ss_encrypt"), new WrapCallback<RegisterContext>() { // inline wrap导出函数 @Override public void preCall(Emulator<?> emulator, RegisterContext ctx, HookEntryInfo info) { Pointer pointer = ctx.getPointerArg(2); int length = ctx.getIntArg(3); byte[] key = pointer.getByteArray(0, length); Inspector.inspect(key, "ss_encrypt key"); } @Override public void postCall(Emulator<?> emulator, RegisterContext ctx, HookEntryInfo info) { System.out.println("ss_encrypt.postCall R0=" + ctx.getLongArg(0)); }});hookZz.disable_arm_arm64_b_branch();hookZz.instrument(module.base + 0x00000F5C + 1, new InstrumentCallback<Arm32RegisterContext>() { @Override public void dbiCall(Emulator<?> emulator, Arm32RegisterContext ctx, HookEntryInfo info) { // 通过base+offset inline wrap内部函数,在IDA看到为sub_xxx那些 System.out.println("R3=" + ctx.getLongArg(3) + ", R10=0x" + Long.toHexString(ctx.getR10Long())); }}); |
hookZz(2)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 | // 加载HookZzIHookZz hookZz = HookZz.getInstance(emulator);hookZz.wrap(module.base + 0x1BD0 + 1, new WrapCallback<HookZzArm32RegisterContext>() { // inline wrap导出函数 @Override // 类似于 frida onEnter public void preCall(Emulator<?> emulator, HookZzArm32RegisterContext ctx, HookEntryInfo info) { // 类似于Frida args[0] Pointer input = ctx.getPointerArg(0); System.out.println("input:" + input.getString(0)); }; @Override // 类似于 frida onLeave public void postCall(Emulator<?> emulator, HookZzArm32RegisterContext ctx, HookEntryInfo info) { Pointer result = ctx.getPointerArg(0); System.out.println("input:" + result.getString(0)); }}); |
Dobby
1 2 3 4 5 6 7 8 9 10 11 12 | Dobby dobby = Dobby.getInstance(emulator);dobby.replace(module.findSymbolByName("ss_encrypted_size"), new ReplaceCallback() { // 使用Dobby inline hook导出函数 @Override public HookStatus onCall(Emulator<?> emulator, HookContext context, long originFunction) { System.out.println("ss_encrypted_size.onCall arg0=" + context.getIntArg(0) + ", originFunction=0x" + Long.toHexString(originFunction)); return HookStatus.RET(emulator, originFunction); } @Override public void postCall(Emulator<?> emulator, HookContext context) { System.out.println("ss_encrypted_size.postCall ret=" + context.getIntArg(0)); }}, true); |
xHook
xHook 是爱奇艺开源的ndroid PLT hook框架,一个针对 Android 平台 ELF (可执行文件和动态库) 的 PLT (Procedure Linkage Table) hook 库。优点是挺稳定好用,缺点是不能Hook Sub_xxx 子函数。文档看https://github.com/iqiyi/xHook
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | IxHook xHook = XHookImpl.getInstance(emulator); // 加载xHook,支持Import hook,xHook.register("libttEncrypt.so", "strlen", new ReplaceCallback() { // hook libttEncrypt.so的导入函数strlen @Override public HookStatus onCall(Emulator<?> emulator, HookContext context, long originFunction) { Pointer pointer = context.getPointerArg(0); String str = pointer.getString(0); System.out.println("strlen=" + str); context.push(str); return HookStatus.RET(emulator, originFunction); } @Override public void postCall(Emulator<?> emulator, HookContext context) { System.out.println("strlen=" + context.pop() + ", ret=" + context.getIntArg(0)); }}, true);xHook.register("libttEncrypt.so", "memmove", new ReplaceCallback() { @Override public HookStatus onCall(Emulator<?> emulator, long originFunction) { RegisterContext context = emulator.getContext(); Pointer dest = context.getPointerArg(0); Pointer src = context.getPointerArg(1); int length = context.getIntArg(2); Inspector.inspect(src.getByteArray(0, length), "memmove dest=" + dest); return HookStatus.RET(emulator, originFunction); }});xHook.register("libttEncrypt.so", "memcpy", new ReplaceCallback() { @Override public HookStatus onCall(Emulator<?> emulator, long originFunction) { RegisterContext context = emulator.getContext(); Pointer dest = context.getPointerArg(0); Pointer src = context.getPointerArg(1); int length = context.getIntArg(2); Inspector.inspect(src.getByteArray(0, length), "memcpy dest=" + dest); return HookStatus.RET(emulator, originFunction); }});xHook.refresh(); // 使Import hook生效 |
Unicorn Hook
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 | emulator.getBackend().hook_add_new(new CodeHook() { @Override public void hook(Backend backend, long address, int size, Object user) { RegisterContext context = emulator.getContext(); //System.out.println(user); //System.out.println(size); if (address == module.base + 0x1FF4){ Pointer md5Ctx = context.getPointerArg(0); Inspector.inspect(md5Ctx.getByteArray(0, 32), "md5Ctx"); Pointer plainText = context.getPointerArg(1); int length = context.getIntArg(2); Inspector.inspect(plainText.getByteArray(0, length), "plainText"); }else if (address == module.base + 0x2004){ Pointer cipherText = context.getPointerArg(1); Inspector.inspect(cipherText.getByteArray(0, 16), "cipherText"); } } @Override public void onAttach(UnHook unHook) { } @Override public void detach() { }}, module.base + 0x1FE8, module.base + 0x2004, "xxxxzzzz"); |
五、 打印调用栈
1 | emulator.getUnwinder().unwind(); |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | public void callFunc() { emulator.getBackend().hook_add_new(new CodeHook() { @Override public void hook(Backend backend, long address, int size, Object user) { System.out.println("开始--------------------------"); System.out.println(user); System.out.println(size); emulator.getUnwinder().unwind(); System.out.println("==============================="); } @Override public void onAttach(UnHook unHook) { } @Override public void detach() { } },module.base+0xAD40,module.base+0xAD40,"xibei");} |

六、Console Debugger
1 2 | Debugger attach = emulator.attach();attach.addBreakPoint(module.base + 0xC365); //断点地址 |

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 | c: 继续n: 跨过bt:回溯st hex:搜索堆栈shw hex:搜索可写堆shr hex:搜索可读堆shx-hex:搜索可执行堆nb:在下一个街区破发s|si:步入s[decimal]:执行指定的金额指令s(blx):执行util blx助记符,性能低m(op)[size]:显示内存,默认大小为0x70,大小可以是十六进制或十进制mr0-mr7,mfp,mip,msp[size]:显示指定寄存器的内存m(address)[size]:显示指定地址的内存,地址必须以0x开头wr0-wr7,wfp,wip,wsp<value>:写入指定寄存器wb(address),ws(address),wi(address)<value>:写入指定地址的(字节、短、整数)内存,地址必须以0x开头wx(address)<hex>:将字节写入指定地址的内存,地址必须以0x开头b(address):添加临时断点,地址必须以0x开头,可以是模块偏移量b: 添加寄存器PC的断点r: 删除寄存器PC的断点blr:添加寄存器LR的临时断点p (assembly):位于PC地址的修补程序集where: 显示java堆栈跟踪trace[begin-end]:设置跟踪指令traceRead[begin-end]:设置跟踪内存读取traceWrite〔begin-end〕:设置跟踪内存写入vm:查看加载的模块vbs:查看断点d|dis:显示反汇编d(0x):在指定地址显示反汇编stop: 停止模拟run[arg]:运行测试gc:运行System.gc()threads: 显示线程列表cc size:将asm从0x4000c364-0x4000c364+size字节转换为c函数 |
七、监控内存读写
将信息输出到文件
1 2 3 4 5 6 7 | String traceFile = "myMonitorFile";PrintStream traceStream = null;try { traceStream = new PrintStream(new FileOutputStream(traceFile), true);} catch (FileNotFoundException e) { e.printStackTrace();} |
监控内存读
1 | emulator.traceRead(module.base, module.base + module.size).setRedirect(traceStream); |
监控内存写
1 | emulator.traceWrite(module.base, module.base + module.size).setRedirect(traceStream); |
执行效果

八、trace
如果代码被混淆,其中90%都是无用的代码,直接看汇编代码,分析会很困难。trace可以将程序运行后,实际用到的汇编代码输出到指定文件中,再去分析。
1 2 3 4 5 6 7 8 | String traceFile = "myTraceCodeFile";PrintStream traceStream = null;try { traceStream = new PrintStream(new FileOutputStream(traceFile), true);} catch (FileNotFoundException e) { e.printStackTrace();}emulator.traceCode(module.base, module.base + module.size).setRedirect(traceStream); |
执行前

执行后效果
