插件『IDA/OD/IMMDbg Plugin』

基于ImmDbg的Python内存注射

没有评论

其实上一篇文章完全是拷贝来的，目的是做个本地备份。 😀 最近开始将一些工作转移到ImmDbg，在此之前是想在OD的脚本中做一些简单的工作来实现一些内存数据的修改以及写入功能，但是事实上由于OD脚本的API函数有限，要实现诸如文件读取之类的工作发现基本没什么可能，当然了也有可能是因为自己孤陋寡闻， :8 如果谁知道相关的APi还望不吝赐教。 smile

Continue Reading

插件『IDA/OD/IMMDbg Plugin』

Starting to write Immunity Debugger PyCommands : my cheatsheet 『Rw』

没有评论

When I started Win32 exploit development many years ago, my preferred debugger at the time was WinDbg (and some Olly). While Windbg is a great and fast debugger, I quickly figured out that some additional/external tools were required to improve my exploit development experience.

Despite the fact that the command line oriented approach in windbg has many advantages, it appeared not the best tool to search for good jump addresses, or to list non-safeseh compiled / non-aslr aware modules, etc….  Ok, looking for a simple “jmp esp” is trivial, but what if you are looking for all pop pop ret combinations in non-safeseh compiled modules…   Not an easy task.

It is perfectly possible to build plugins for Windbg, but the ones that I have found (MSEC, byakugan (Metasploit)) don’t always work the way I want them to work, and would still not solve some issues I was having while writing exploits.

OllyDbg and Immunity Debugger are quite different than windbg.  Not only the GUI is very much different, the number of plugins for these debuggers is substantially higher.  After evaluating both of them (they pretty much have the same look and feel), and evaluating the way plugins can be added, I made the decision to focus on Immunity Debugger.

That does not mean OllyDbg is a bad debugger or is limited in what you can do in terms of writing plugins… I just found it harder to “quickly tweak a plugin” while building an exploit.   OllyDbg plugins are compiled into dll’s, so changing a plugin would require me to recompile and test.   Immunity Debugger uses python scripts.  I can go into the script, make a little change, and see the results right away.  Simple.

Continue Reading

破解/汇编『Crack/Asm』, 程序设计『Programing』

Calling IDA APIs from IDAPython with ctypes

没有评论

IDAPython 提供了一些列封装好的ida sdk函数，但是由于SWIG的限制或者一切其他的原因有一部分api并没有封装到这个库中。为了能够调用在idapython中没有封装的api函数get_loader_name()，但是又不想因为调用这么一个简单的函数而编写一个插件进行测试，那么此时就可以使用ctypes 来实现了。

所有IDA API都是由ida的核心动态库来提供的，在Windows系统下这个库为ida.wll（或者ida64.wll），在linux系统下为libida[64].so,在os x系统下为libida[64].dylib. ctypes提供了一个非常好的功能来创建一个封装的Dll到处函数类，可以把他们看成一个类实例的属性来调用。下面的代码用于获取不同系统下的ida实例：

import ctypes
import sys
idaname = "ida64" if __EA64__ else "ida"
if sys.platform == "win32":
dll = ctypes.windll[idaname + ".wll"]
elif sys.platform == "linux2":
dll = ctypes.cdll["lib" + idaname + ".so"]
elif sys.platform == "darwin":
dll = ctypes.cdll["lib" + idaname + ".dylib"]

我们使用windll是因为ida的api在windows系统下是使用stdcall调用约定的（可以通过查看pro.h中队用的idaapi的定义来确定调用类型）

现在我们只需要像调用一个dll对象的一个属性一样来调用我们的函数，但是首先我们要准备好我们函数需要的参数，下面是从loader.hpp中得到的函数的定义：

idaman ssize_t ida_export get_loader_name(char *buf, size_t bufsize);

ctypes提供了一个非常方便的函数来创建字符buffer：

buf = ctypes.create_string_buffer(256)
Continue Reading
Close Menu