Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

订阅源联系隐私© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
rhabdomancer — Vulnerability research assistant that locates calls to potentially insecure API functions in a binary file. | Kitploit
工具/GitHubGitHub/0xdea/rhabdomancer
Static AnalysisVulnerability AnalysisReverse EngineeringBinary Analysis
GitHub0xdea/rhabdomancer

rhabdomancer

Vulnerability research assistant that locates calls to potentially insecure API functions in a binary file.

查看仓库网站
131155312小时25分前Kitploit 审核通过
分享
内容在请求的语言中不可用。显示英文版本。

rhabdomancer

build doc

"The road to exploitable bugs is paved with unexploitable bugs."

-- Mark Dowd

Rhabdomancer is a blazing-fast IDA headless plugin that locates calls to potentially insecure API functions in a binary file. Auditors can backtrace from these candidate points to find pathways allowing access to untrusted input.

Features

  • Blazing-fast, headless user experience courtesy of IDA 9.x and idalib-rs Rust bindings.
  • Support for C/C++ binary targets compiled for any architecture implemented by IDA.
  • Bad API function call locations are printed to stdout and marked in the IDB.
    • Call locations in library code recognized by IDA (e.g., a statically linked runtime matched by FLIRT signatures) are labeled (lib).
    • Calls through stubs (e.g., the .plt entries of ELF binaries or the import stubs of PE and Mach-O binaries, listed as thunks) are traced back to their callers.
    • In ELF binaries, a function is deliberately listed twice with the same call locations: once as its .plt stub (marked as thunk) and once as its import. Each call location is marked only once in the IDB.
  • Known bad API functions are grouped in tiers of badness to help prioritize the audit work.
    • [BAD 0] High priority - Functions that are generally considered insecure.
    • [BAD 1] Medium priority - Interesting functions that should be checked for insecure use cases.
    • [BAD 2] Low priority - Code paths involving these functions should be carefully checked.
  • The list of known bad API functions is built in and can be easily customized with a configuration file based on conf/rhabdomancer.toml.
  • Function names are matched without these decorations: the # marking native ARM64EC functions (e.g., #memcpy), the variant suffixes of Apple's SDK (e.g., realpath$DARWIN_EXTSN, stat$INODE64), the size of the arguments that 32-bit x86 calling conventions append (e.g., _WinExec@8), leading dots and underscores (e.g., _strcpy), the prefixes of library aliases and redirects (e.g., __o_malloc in the Universal CRT, __libc_system, __GI___snprintf, _IO_fwrite, and __isoc23_sscanf in glibc, also in ELF .plt stubs such as .__isoc23_sscanf), and, for stubs and such aliases only, the numeric suffix that IDA appends to names already in use (e.g., memset_0). In custom configurations, a leading #, Apple's variant suffixes, the size of the arguments, dots, and underscores are ignored as well, and each name may be listed under one priority only.

[!NOTE] Fortified functions (e.g., __strcpy_chk, used instead of strcpy when building with _FORTIFY_SOURCE) are deliberately not matched, since they are the checked variants of the listed functions. To also mark their calls, add them explicitly to a custom configuration (e.g., "__strcpy_chk" with the same priority as strcpy). The same works for other redirected names that rhabdomancer doesn't map to their base function yet (e.g., "__xstat" for stat): they are matched by name, and labeled with it once normalized (e.g., [BAD 2] xstat).

Articles

  • https://hex-rays.com/blog/divining-vulnerabilities-contributor-program
  • https://hex-rays.com/blog/streamlining-vulnerability-research-idalib-rust-bindings
  • https://hnsecurity.it/blog/streamlining-vulnerability-research-with-ida-pro-and-rust

See also

  • https://github.com/0xdea/ghidra-scripts/blob/main/Rhabdomancer.java
  • https://docs.hex-rays.com/release-notes/9_0#headless-processing-with-idalib
  • https://github.com/idalib-rs/idalib
  • https://books.google.it/books/about/The_Art_of_Software_Security_Assessment.html

Installing

The easiest way to get the latest release is via crates.io:

  1. Download, install, and configure IDA (see https://hex-rays.com/ida-pro).
  2. Install LLVM/Clang (see https://rust-lang.github.io/rust-bindgen/requirements.html).
  3. On Linux/macOS, install as follows:
    export IDADIR=/path/to/ida # if not set, the build script will check common locations
    cargo install rhabdomancer --locked
    
    On Windows, instead, use the following commands:
    $env:LIBCLANG_PATH="\path\to\clang+llvm\bin"
    $env:PATH="\path\to\ida;$env:PATH"
    $env:IDADIR="\path\to\ida" # if not set, the build script will check common locations
    cargo install rhabdomancer --locked
    

Compiling

Alternatively, you can build from source:

  1. Download, install, and configure IDA (see https://hex-rays.com/ida-pro).
  2. Install LLVM/Clang (see https://rust-lang.github.io/rust-bindgen/requirements.html).
  3. On Linux/macOS, compile as follows:
    git clone --depth 1 https://github.com/0xdea/rhabdomancer
    cd rhabdomancer
    export IDADIR=/path/to/ida # if not set, the build script will check common locations
    cargo build --release --locked
    
    On Windows, instead, use the following commands:
    git clone --depth 1 https://github.com/0xdea/rhabdomancer
    cd rhabdomancer
    $env:LIBCLANG_PATH="\path\to\clang+llvm\bin"
    $env:PATH="\path\to\ida;$env:PATH"
    $env:IDADIR="\path\to\ida" # if not set, the build script will check common locations
    cargo build --release --locked
    

Usage

  1. Make sure IDA is properly configured with a valid license.
  2. Optionally customize the list of known bad API functions: copy conf/rhabdomancer.toml (pick the tag that matches your installed version for its exact built-in list), edit the copy, and set the RHABDOMANCER_CONFIG environment variable to its path. The file must define the high, medium, and low arrays, and no other keys. Otherwise, the built-in list is used, which is embedded in the binary at build time from conf/rhabdomancer.toml (editing that file requires a rebuild).
  3. Make sure the IDADIR environment variable is set if your IDA installation is in a non-standard location.
  4. Run as follows:
    rhabdomancer <binary_file>
    
    Any existing .i64 IDB file will be updated; otherwise, a new IDB file will be created.
  5. Open the resulting .i64 IDB file with IDA.
  6. Select View > Open subviews > Bookmarks
  7. Enjoy your results conveniently collected into an IDA window.

[!NOTE] Rhabdomancer also adds comments at marked call locations. Both bookmarks and comments are tagged as [BAD n] <function_name>, where n is the priority tier (0 = high, 1 = medium, 2 = low), so that scripts can search IDBs for them. This format is stable across releases.

Compatibility

Only the latest IDA release is officially supported, but older versions may work as well. The following table summarizes the latest compatible release for each IDA version:

下载工具

最受欢迎

查看全部 →

发现我们社区最常用的工具。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 终极 OSINT 工具包:调查图谱、置信度评分、别名家族、地图、时间线和报告。49 个模块、400+ 个站点,无需 API 密钥。

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    429
  • 4

    redforge

    cybersecurity91/redforge

    浏览器端红队工具包,包含 102 个离线工具,用于侦察、载荷生成、凭据攻击、加密、编码和交战报告。

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI原生网络安全的行动系统——在这里,意图转化为受治理的执行,证据沉淀为运营记忆,每一次操作都让下一次更出色。

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT 平台,可将 Shadowserver 报告导入 MongoDB,并将其重放为交互式地图、分析、发现、公告和高管仪表板。

    256

探索所有工具

浏览我们的工具集合

查看所有工具 →