Acunetix
Web vulnerability scanner for automated security testing of websites and web apps
BinAbsInspector
Static binary analyzer for automated vulnerability detection via abstract interpretation
BinAbsInspector is a static binary analyzer that leverages abstract interpretation on Ghidra Pcode to automatically detect multiple CWE vulnerabilities across x86, x64, ARMv7, and AArch64 binaries.
Overview
Overview
BinAbsInspector is a static analysis tool built on top of Ghidra that uses abstract interpretation of Ghidra's Pcode to scan binaries for security weaknesses. It supports the major architectures—x86, x64, ARMv7, and AArch64—and includes checkers for over a dozen CWE classes such as command injection, buffer overflows, use‑after‑free, and integer overflows.
Who It Serves & How to Deploy
The tool is aimed at security researchers, reverse‑engineers, and development teams that need automated binary‑level vulnerability assessment. It can be run in three modes: directly within Ghidra’s GUI, via Ghidra’s headless command‑line interface, or inside a Docker container for CI/CD integration. Installation requires Ghidra, a compatible Z3 SMT solver, and Java/Gradle for building the extension.
Extensibility
Implemented in Java, BinAbsInspector’s source is organized for easy extension. New checkers can be added in the com.bai.checkers package and the extension rebuilt with Gradle, allowing custom security rules to be incorporated alongside the existing CWE suite.
Highlights
Abstract interpretation on Ghidra Pcode for architecture‑agnostic analysis
Built‑in checkers for 15+ CWE vulnerability classes
Runs in GUI, headless, or Docker environments
Integrates Z3 SMT solver for precise constraint solving
Pros
- High precision thanks to abstract interpretation
- Leverages Ghidra’s extensive binary support
- Extensible Java codebase with Gradle build
- Multi‑architecture coverage (x86, x64, ARMv7, AArch64)
Considerations
- Requires Ghidra and Z3 setup before use
- Java/Gradle build may be complex for beginners
- Analysis speed can be limited by Z3 timeouts
- Currently limited to the provided CWE checkers
Managed products teams compare with
When teams consider BinAbsInspector, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Security researchers performing binary vulnerability audits
- Reverse engineers needing automated CWE detection
- Teams integrating static analysis into CI pipelines via Docker
- Developers targeting x86, x64, ARMv7, and AArch64 binaries
Not ideal when
- Users seeking source‑code level analysis
- Environments without Java or Ghidra installed
- Real‑time analysis of large codebases where performance is critical
- Projects requiring custom vulnerability rules beyond the existing CWE set
How teams use it
Automated security audit of legacy firmware
Identify buffer overflows, integer overflows, and use‑after‑free bugs across ARM binaries without source code.
CI integration for binary release validation
Run BinAbsInspector in Docker to fail builds when new CWE violations are detected.
Educational reverse‑engineering labs
Students can visualize CWE reports directly in Ghidra GUI, linking findings to code locations.
Research on abstract interpretation techniques
Extend or add new checkers using the Java API and evaluate precision against known vulnerable samples.
Tech snapshot
Java99%
Dockerfile1%
Frequently asked questions
What architectures does BinAbsInspector support?
It currently supports x86, x64, ARMv7, and AArch64 binaries.
Do I need a Ghidra license to use it?
No, BinAbsInspector runs as a Ghidra extension and uses the free Ghidra distribution.
How is Z3 used in the analysis?
Z3 serves as the SMT solver for constraint solving during abstract interpretation; you must install a compatible Z3 version (e.g., 4.8.15).
Can I run the analyzer without a GUI?
Yes, BinAbsInspector offers headless mode via Ghidra’s analyzeHeadless script and a Docker image for fully automated execution.
How can I add custom vulnerability checkers?
The project is built with Gradle and Java; you can implement new checkers in the `com.bai.checkers` package and rebuild the extension.
Project at a glance
Dormant- Stars
- 1,667
- Watchers
- 1,667
- Forks
- 245
LicenseGPL-3.0
Repo age3 years old
Last commit2 years ago
Primary languageJava
Last synced yesterday