MAMBO: A Low-Overhead Dynamic Binary Modification Tool for RISC architectures

News

• 2024-02-04: We presented MAMBO in the RISC-V devroom at FOSDEM 2024 in Brussels, Belgium. The recording of our talk in available here.
• 2024-01-17: We presented a MAMBO tutorial at HiPEAC 2024 in Munich, Germany. All materials are available here.
• 2023-04-24: We presented in ISPASS 2023 our paper "Evaluating the Impact of Optimizations for Dynamic Binary Modification on 64-bit RISC-V".
• 2021-09-21: We've released a partial port of MAMBO to RISC-V in the riscv branch, where development is continuing. The initial porting was done by Guillermo Callaghan and Cosmin Gorgovan.
• 2021-02-24: PhD opportunities related to MAMBO and security available. If interested, contact mikel.lujan at manchester.ac.uk with the subject APT MAMBO PhD [your surname]
• 2020-03-16: We've presented (virtually) our VEE paper about AArch64 optimizations in MAMBO. The talk is available on youtube.
• 2020-02-22: We've presented our CC paper about MAMBO's API (see Publications and Plugin API below) and the cachesim (an online cache simulator) and memcheck (a memory error checker) plugins. The slides are available here.
• 2018-04-11: We've presented our ICPE paper. The slides are available here.
• 2018-01-23: We've ran a tutorial on using MAMBO's API at HiPEAC 2018. The slides are available here.
• 2017-04-24: An address decoder for load and store instructions was added to the API: mambo_calc_ld_st_addr(). It allows plugin developers to automatically obtain the base address of all data memory accesses. This API function is available for all supported instruction sets: A32, T32, A64. Its usage is demonstrated in the plugins/mtrace.c plugin.
• 2017-04-04: Significantly improved support for Linux signals was implemented.
• 2017-04-03: The AArch64 port of MAMBO is officially released. The initial AArch64 porting was done by Guillermo Callaghan .
• 2017-01-25: We have presented the TACO paper at HiPEAC 2017, on 25th of January. The slides are available here.

Publications

• Cosmin Gorgovan, Amanieu d’Antras, and Mikel Luján. 2016. MAMBO: A low-overhead dynamic binary modification tool for ARM. ACM Trans. Archit. Code Optim. 13, 1, Article 14 (April 2016). Open access. If you use MAMBO for your research, please cite this paper.

• Cosmin Gorgovan, Amanieu d’Antras, and Mikel Luján. 2018. Optimising Dynamic Binary Modification Across ARM Microarchitectures. In Proceedings of the 2018 ACM/SPEC International Conference on Performance Engineering (ICPE '18). Free download via research.manchester.ac.uk.

• Cosmin Gorgovan, Guillermo Callaghan, and Mikel Luján. Balancing Performance and Productivity for the Development of Dynamic Binary Instrumentation Tools - A Case Study on Arm Systems. In Proceedings of the 29th International Conference on Compiler Construction (CC '20) Free download via research.manchester.ac.uk.

• Guillermo Callaghan, Cosmin Gorgovan and Mikel Luján. Optimising dynamic binary modification across 64-bit Arm microarchitectures. In Proceedings of the 16th ACM SIGPLAN/SIGOPS International Conference on Virtual Execution Environments (VEE '20) Free download via research.manchester.ac.uk.

• John Alistair Kressel, Guillermo Callaghan, Cosmin Gorgovan, and Mikel Luján. (2023). Evaluating the Impact of Optimizations for Dynamic Binary Modification on 64-bit RISC-V. In 2023 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS) IEEE. Free download via research.manchester.ac.uk.

MAMBO was created as part of Cosmin's EPSRC-funded PhD in the School of Computer Science at the University of Manchester. MAMBO has been previosly developed as part of the PAMELA EP/K008730/1 and DOME EP/J016330/1 EPSRC projects. MAMBO is currently supported by the UK Industrial Strategy Challenge Fund (ISCF) under the Digital Security by Design (DSbD) Programme delivered by UKRI as part of the MoatE (10017512) and Soteria (75243) projects.

Status

MAMBO's compatibility with applications is continuously being improved as needed. We are using it on ARMv7 and ARMv8 and RISC-V64GC systems. Our ARM systems run the armhf / arm64 builds of Debian, Ubuntu and Arch Linux ARM. Our RISC-V systems use Ubuntu 22.04 for RISC-V 64-bit. Most GNU/Linux applications work correctly. The following more complex applications and benchmark suites are working correctly under MAMBO on ARM systems (this is not an exhaustive list):

• SPEC CPU2006
• PARSEC 3.0
• SLAMBench
• GCC (GCC running under MAMBO can build MAMBO)
• LibreOffice
• GIMP
• SuperTuxKart
• XMoto

Also read the Known issues section below.

Build

Prerequisites: an ARM or RISC-V64GC system (physical or virtual) to build and run MAMBO on; dependencies: gcc toolchain, libelf(-dev), ruby (>=1.9.1). Debian or Ubuntu users can install the required packages with sudo apt-get install build-essential libelf-dev ruby.

git clone https://github.com/beehive-lab/mambo.git
cd mambo
make

Usage

To launch an application under MAMBO, run:

./dbm <path_to_executable> [application's command line arguments]

For example to run ls -a under MAMBO, execute:

./dbm /bin/ls -a

Tip: When an application running under MAMBO exits, the string We're done; exiting with status: <APPLICATION'S EXIT CODE> will be printed to stderr.

Plugin API

The plugin API is event-driven. Plugins should use an initialisation function with __attribute__((constructor)) to register themselves using mambo_register_plugin(). Once a plugin is registered, it can install callbacks for various events using the mambo_register_*_cb() functions. Callback-related functions are listed in api/plugin_support.h. Code generation helpers are listed in api/helpers.h and code generation functions are listed in api/emit_<INST SET>.h headers, which are generated at build-time).

Sample plugins are available in the plugins/ directory.

To build MAMBO with plugin support, the source code or object file(s) of the plugin you're trying to build must be added to the PLUGINS= line in the makefile, or provided as an argument/envvar. Note that multiple plugins can be enabled at the same time (and will work correctly if properly designed). For performance reasons, it is recommended to remove unused plugins from the PLUGINS= list. Additional arguments that are required to build the plugins can be provided through PLUGIN_ARGS.

Known issues

• There are two limitations related to signal handling: the data in the siginfo_t structure passed to SA_SIGINFO signal handlers is incorrect: most signals will appear to have been sent via kill() from the application itself; and synchronous signal (SIGSEGV, SIGBUS, SIGFPE, SIGTRAP, SIGILL, SIGSYS) handlers cannot sigreturn(), but can (sig)longjmp().
• At the moment, code cache invalidation in response to the munmap and __cache_flush system calls are only done in the thread in which the system call is executed. This can potentially lead to execution of stale cached code in other threads.
• MAMBO on RISC-V systems does not have full signal handling capabilities. This will cause complex applications, such as GIMP, to experience issues.

Reporting bugs

If you think you have found a bug which is not in the list of Known issues, please report it here, on Github. However, note that we have limited time available to investigate and fix bugs which are not affecting the workloads we are using. Therefore, if you can't pinpoint the cause of the bug yourself, we ask that you provide as many details on how to reproduce it, and preferably provide a statically linked executable which triggers it.

Contributions

We welcome contributions. Use pull requests on Github. However, note that we are doing most development in a private git tree and we are working on a number of features which are not quite ready for public release. Therefore, we would strongly encourage you to get in touch before starting to work on anything large, to avoid duplication of effort. We can probably expedite our release of any WIP features you might be interested in, if you do that.

Sandboxing

Note that similarly to most other DBM / DBI frameworks and to optimise performance / development effort, MAMBO is not designed to secure itself against malicious activity from the application it is translating. This means that without hardening MAMBO itself, it would not be possible to use it to implement a secure sandbox.