Skip to content

Interactive dependency map

Jump to bottom
Michael Messner edited this page Mar 27, 2026 · 13 revisions

With version 2.0.1 EMBA got an interactive dependency map.

image

This module is automatically enabled in the default scanning profile. To control this module the profile parameter EMBA_MAP_GENERATOR=1 can be used to enable/disable this feature.

image

This module has multiple mechanisms for the identification of dependencies integrated:

  • ldd
  • objdump
  • str with "/" characters
  • fuzzy strings
  • user-mode emulation
  • system mode emulation

With a helper function it is also possible to run it standalone after the firmware analysis with EMBA is finished:

└─$ ./helpers/firmware_map_builder.sh -e <EMBA log directory>

Additionally, it is also possible to run it without an EMBA scan on an extracted firmware image directory:

└─$ ./helpers/firmware_map_builder.sh -f <firmware directory> -l <log directory>

EMBA - firmware security scanning at its best

Sponsor EMBA and EMBArk:

The EMBA environment is free and open source!

We put a lot of time and energy into these tools and related research to make this happen. It's now possible for you to contribute as a sponsor!

If you like EMBA you have the chance to support future development by becoming a Sponsor

Thank You ❤️ Get a Sponsor
You can also buy us some beer here ❤️ Buy me a coffee

To show your love for EMBA with nice shirts or other merch you can check our Spreadshop

EMBA - firmware security scanning at its best

Clone this wiki locally