Jump to content

Binary Ninja

From Wikipedia, the free encyclopedia
Binary Ninja
Original author(s)Jordan Wiens, Rusty Wagner, Peter LaFosse
Developer(s)Vector 35 Inc[1]
Initial releaseJuly 31, 2016; 8 years ago (2016-07-31)[2]
Stable release
4.1.5747 / July 17, 2024; 3 months ago (2024-07-17)[2]
Written inC++, C, Python, Rust
Operating systemMicrosoft Windows, Mac OS X, and Linux
Available inEnglish
TypeReverse Engineering, Disassembler, Decompiler
LicenseProprietary
Websitehttps://binary.ninja

Binary Ninja is a reverse-engineering platform developed by Vector 35 Inc.[1] It can disassemble a binary and display the disassembly in linear or graph views. It performs automated in-depth analysis of the code, generating information that helps to analyze a binary. It lifts the instructions into intermediate languages, and eventually generates the decompiled code.

Binary Ninja supports various CPU architectures and binary executable formats. It runs on Windows, macOS, and Linux. It also has a free-to-use cloud and native version.[3]

History

[edit]

Binary Ninja was originally an internal tool[4] for a CTF team. The developers later decided to form Vector 35 Inc and develop Binary Ninja into a commercial product. The development started in 2015 and the first public version was released in July 2016.

The commercial product does not share code[4] with the internal tool. The latter one is now open-sourced[5] under GPLv2.

Features and usage

[edit]

User interface

[edit]

Binary Ninja's UI is built using Qt. Its main UI comprises a symbol list, a cross-reference window, a linear/graph view of the disassembly, a mini-graph, as well as a feature map. It can also show a hex editor, strings listing, and a triage view.

Binary Ninja generates extensive annotations in the UI to assist binary analysis.

Binary Ninja also supports user-defined themes.[6]

API and plugins

[edit]

Binary Ninja offers an API that can be accessed via Python, C++, or Rust.[7] The API is open-sourced[8] under MIT License. It can interact with most of the Binary Ninja's functionality, e.g., user interface, analysis, IL (see below), etc. It can be used to add support for new architecture or automate tasks.

Plugins[9] can be made via the API to enhance Binary Ninja. Vector35 maintains a collection of official plugins,[10] while the community has created numerous community plugins.[11]

Some notable plugins are the debugger,[12] the signature kit,[13] etc.

Binary Ninja intermediate languages (BNIL)

[edit]

Binary Ninja offers three intermediate languages (ILs).

  • The low-level IL (LLIL)[14] is a verbose lifting of the underlying instructions from various architectures to a unified representation.
  • The medium-level IL (MLIL)[15] creates variables with types and removes the notion of the stack.
  • The high-level IL (HLIL, also called decompiler) offers a representation of the code that is similar to C source code.

Core analysis

[edit]

Binary Ninja automatically performs various analyses on the binary. Some examples are:

  • function detection
  • cross-references for code and data
  • type inference
  • constant propagation
  • value-set analysis
  • jump table resolution

Binary editing and patching, shellcode compiler (SCC)

[edit]

Binary Ninja offers binary patching and editing features. It can assemble an instruction at the current line, flip a conditional jump, etc. Edits and updated analysis are immediately reflected in the UI.

Binary Ninja can be used as a general binary editor. It supports several commonly-used transformations and encryption algorithms.

The shellcode compiler allows the user to compile and insert code via C syntax.

Supported architectures and executable file formats

[edit]

Architectures

[edit]

Binary Ninja supports the following CPU architectures officially:

  • x86 32-bit
  • x86 64-bit
  • ARMv7
  • Thumb2
  • ARMv8
  • PowerPC
  • MIPS
  • RISC-V
  • 6502
  • nanoMIPS
  • TriCore

The support for these architectures vary and details can be found in the official FAQ.[16]

Community-authored plugins add support for various other architectures.[17]

Executable file formats

[edit]

Binary Ninja supports the following executable file formats officially:

  • PE/COFF
  • ELF
  • Mach-O
  • .NES binary (via a plugin)
  • Raw binary
  • md1rom

See also

[edit]

References

[edit]
  1. ^ a b "Vector 35 > home". vector35.com. Retrieved 2020-07-26.
  2. ^ a b Vector 35 Inc. "Binary Ninja > Binary Ninja > changelog". binary.ninja. Retrieved 2020-07-26.
  3. ^ "Try Binary Ninja". binary.ninja. Retrieved 2024-03-02.
  4. ^ a b "Binary Ninja > Frequently Asked Questions". faq.binary.ninja. Retrieved 2020-07-26.
  5. ^ Vector35/deprecated-binaryninja-python, VECTOR 35, 2020-07-12, retrieved 2020-07-26
  6. ^ Vector35/community-themes, VECTOR 35, 2020-07-09, retrieved 2020-07-26
  7. ^ "Using the Binary Ninja API - Binary Ninja User Documentation". docs.binary.ninja. Retrieved 2023-03-17.
  8. ^ Vector35/binaryninja-api, VECTOR 35, 2020-07-22, retrieved 2020-07-26
  9. ^ "Using and Writing Plugins - Binary Ninja User Documentation". docs.binary.ninja. Retrieved 2020-07-26.
  10. ^ Vector35/official-plugins, VECTOR 35, 2020-07-16, retrieved 2020-07-26
  11. ^ "Using and Writing Plugins - Binary Ninja User Documentation". docs.binary.ninja. Retrieved 2020-07-26.
  12. ^ Vector35/debugger, VECTOR 35, 2020-07-25, retrieved 2020-07-26
  13. ^ Vector35/sigkit, VECTOR 35, 2020-07-14, retrieved 2020-07-26
  14. ^ "BNIL Guide: LLIL - Binary Ninja User Documentation". docs.binary.ninja. Retrieved 2020-07-26.
  15. ^ "BNIL Guide: MLIL - Binary Ninja User Documentation". docs.binary.ninja. Retrieved 2020-07-26.
  16. ^ "Binary Ninja > Frequently Asked Questions". binary.ninja. Retrieved 2024-07-25.
  17. ^ Vector35/community-plugins, VECTOR 35, 2020-07-22, retrieved 2020-07-26