EMBA is designed to help penetration testers in analyzing firmware for security vulnerabilities. During such a firmware analysis numerous tools are used, e.g. binwalk, cve-search or yara (and many others).
EMBA combines these tools under its hood and can be started with one simple command. Afterwards it tests the firmware for possible security risks and interesting areas for further investigation. If the firmware has not yet been extracted, this is done automatically by EMBA. No cumbersome installation of all helpers, once the installation script has been executed, you are ready to test your firmware. One of the most important aspects of development is that EMBA is easy to use and easy to set up at all times.
EMBA is designed to assist penetration testers and not as a standalone tool without human interaction. EMBA should provide as much information as possible about the firmware, that the tester can decide on focus areas and is responsible for verifying and interpreting the results.
Before running EMBA make sure, that you have installed all dependencies with the installation script and met the prerequisites
git clone https://github.com/e-m-b-a/emba.git
cd emba
sudo ./installer.sh -dsudo ./emba.sh -l ./log -f /firmwaresudo ./emba.sh -l ./log -f /firmware -p ./scan-profiles/default-scan.emba
./emba.sh -l ./log -f ./firmware -DWARNING: Before using the developer mode you need a full installation of emba with sudo ./installer.sh -F. Such a full installation needs around 14gig of disk space.
EMBA supports multiple arguments. For more details check the wiki.
The IoT is growing, the development is ongoing, and there are many new features that we want to add. We welcome pull requests and issues on GitHub.