# MUI | A GUI Plugin For Binary Ninja To Easily Interact With And View The Progress Of Manticore **URL:** \ **Category:** Tools & Scripts\ **Tags:** tools\ **Created:** [January 3, 2022, 4:06pm UTC](https://onehack.st/t/mui-a-gui-plugin-for-binary-ninja-to-easily-interact-with-and-view-the-progress-of-manticore/211174 "2022-01-03T16:06:45Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Astrid](https://onehack.st/user_avatar/onehack.st/astrid/32/174869_2.png) [@Astrid](https://onehack.st/u/Astrid)\ **Post date:** [January 3, 2022, 4:06pm UTC](https://onehack.st/t/mui-a-gui-plugin-for-binary-ninja-to-easily-interact-with-and-view-the-progress-of-manticore/211174/1 "2022-01-03T16:06:45Z")
[![Manticore](https://raw.githubusercontent.com/trailofbits/manticore/master/docs/images/manticore.png)](https://raw.githubusercontent.com/trailofbits/manticore/master/docs/images/manticore.png) With the Manticore User Interface (MUI) project, we provide a graphical user interface plugin for [Binary Ninja](https://binary.ninja/) to allow users to easily interact with and view progress of the [Manticore symbolic execution engine](https://github.com/trailofbits/manticore) for analysis of smart contracts and native binaries. ❗ATTENTION​:red\_exclamation\_mark: This project is under active development and may be unstable or unusable. Please open an issue if you have any difficulties using the existing features. New feature development will be considered on a case by case basis. ## Requirements Aside from the Python requirements, we require the following: - Binary Ninja (latest development version) with GUI - `git submodule update --init --recursive` for Manticore submodule ## Installation MUI requires a copy of Binary Ninja with a GUI. Currently we are testing against the latest `dev` release(s) (`2.4.2901-dev` at time of writing). Manticore only operates on native binaries within a Linux environment. EVM support has only been tested on Mac and Linux, and it requires the installation of [ethersplay](https://github.com/crytic/ethersplay). Python dependencies are currently managed using `requirements.txt` and `requirements-dev.txt`. You can run `make init` to set up a development environment. 1. Make the project available to Binary Ninja by creating a symbolic link to the plugins directory. From within the root of this repo, run the following: # For Mac $ ln -s “$(pwd)/mui” “${HOME}/Library/Application Support/Binary Ninja/plugins/mui” # For Linux $ ln -s “$(pwd)/mui” “${HOME}/.binaryninja/plugins/mui” 1. Make sure Binary Ninja knows about our Python virtual environment. 2. Open Binary Ninja’s “Preferences” → “Settings” → “Python” and ensure the “Python Interpreter” is correctly set to the Python path associated with the current virtual environment. Reference `venv/pyvenv.cfg` to find the base path. 3. Copy and paste the absolute path of the MUI project into Binary Ninja’s “Python Virtual Environment Site-Packages” and add the required `/venv/lib/python3./site-packages` suffix for the site-packages path. 4. Restart Binary Ninja if necessary. ## Development Installing currently listed dependencies: $ make init # For Mac (will be similar for Linux) $ export PYTHONPATH=“/Applications/Binary Ninja.app/Contents/Resources/python:/Applications/Binary Ninja.app/Contents/Resources/python3” Activating the python virtual environment (do this before running other make commands): $ . venv/bin/activate Code style and linting can be followed by running the following: $ make format $ make lint Tests for code without Binary Ninja interaction can be run if you have a headless version of binary ninja available, otherwise only non-Binary Ninja tests will be run: $ make test Adding a new dependency can be done by editing `requirements.txt` or `requirements-dev.txt` and then running the following in the virtual environment: $ pip install -r requirements-dev.txt -r requirements.txt ## Usage (Native) All MUI features can be accessed through either the right-click context menu or the command palette. Common features include: - Find Path to This Instruction / Remove Instruction from Find List - Avoid This Instruction / Remove Instruction from Avoid List - Add/Edit Custom Hook - Solve With Manticore / Stop Manticore And the following widgets are available: - State List Widget > Shows all the Active/Waiting/Complete/Errored states during manticore execution. Double-clicking a certain state navigates you to the current instruction of that state and renders its provenance tree in the graph widget. [![List widget](https://github.com/trailofbits/MUI/raw/master/screenshots/list_widget.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/list_widget.png) - State Graph Widget > Shows the provenance tree for a certain state selected in the list widget. `Tab` can be used to expand/collapse the graph and double-clicking any of the state nodes navigates you to the current instruction of that state. [![Graph widget](https://github.com/trailofbits/MUI/raw/master/screenshots/graph_widget.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/graph_widget.png) - Run Dialog > The run dialog is shown when you invoke the `Solve with Manticore` command. It allows you to configure the various manticore options, and the changes will be saved to the `bndb` file. Some example configs include using a combination of `LD_PRELOAD` and `LD_LIBRARY_PATH` environment variables to run the binary with custom glibc. [![Run Dialog](https://github.com/trailofbits/MUI/raw/master/screenshots/run_dialog.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/run_dialog.png) - Custom Hook Dialog > The custom hook dialog can be accessed using the `Add/Edit Custom Hook` command. It allows you to define a custom manticore hook at the selected address. You also have full access to the Binary Ninja API which allows you to add highlighting, comments, and more. A defined hook can be removed by setting the code input field to blank. [![Custom Hook Dialog](https://github.com/trailofbits/MUI/raw/master/screenshots/custom_hook.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/custom_hook.png) ## Usage (EVM) EVM support is currently a bit limited. MUI EVM only supports the same feature set as the [Manticore CLI tool](https://github.com/trailofbits/manticore). Available commands include: - Load Ethereum Contract - Solve With Manticore / Stop Manticore And the following views are implemented: - EVM Run Dialog > The run dialog is shown when you invoke the `Solve with Manticore` command. It allows you to configure the various manticore options, and the changes will be saved to the `bndb` file. [![EVM Run Dialog](https://github.com/trailofbits/MUI/raw/master/screenshots/evm_run_dialog.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/evm_run_dialog.png) - Run Report > The report page shows the result of a manticore execution. It displays all the files produced using the Binary Ninja UI. [![Run Report](https://github.com/trailofbits/MUI/raw/master/screenshots/evm_run_report.png)](https://github.com/trailofbits/MUI/blob/master/screenshots/evm_run_report.png) ## GitHub: [https://github.com/trailofbits/MUI](https://github.com/trailofbits/MUI)