An open-source firmware security analyzer for embedded Linux devices, performing extraction, static/dynamic analysis, SBOM generation, and vulnerability reporting.
EMBA is an open-source firmware security analyzer specifically designed for embedded Linux devices. It automates the security assessment process by extracting firmware, performing static and dynamic analysis, generating SBOMs, and producing detailed vulnerability reports. It helps identify weaknesses like insecure binaries, outdated software, and hard-coded credentials in firmware images.
Penetration testers, product security teams, embedded developers, and responsible product managers working with IoT or embedded device firmware who need to assess security risks.
EMBA provides a fully automated, end-to-end firmware analysis pipeline in a single command-line tool, combining extraction, static/dynamic analysis, SBOM generation, and web reporting—all open-source and self-hostable, unlike fragmented or commercial alternatives.
EMBA - The firmware security analyzer
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automates the entire firmware security process from extraction to web-based reporting, as outlined in the key features, reducing manual effort.
Scans for insecure binaries, outdated components, and hard-coded passwords through static analysis, specifically targeting common firmware vulnerabilities.
Performs runtime security testing by emulating firmware, enabling detection of vulnerabilities during execution, with dedicated scan profiles for emulation.
Creates detailed Software Bill of Materials to inventory components, aiding in dependency tracking and compliance, as highlighted in the SBOM profile quick start.
Requires root privileges and a dependency-heavy setup via installer script, which can be error-prone and time-consuming for new users.
As a Bash-based tool, EMBA is restricted to Linux environments, excluding native support for Windows or macOS without virtualization.
Despite automation, the README emphasizes that results require manual verification and expert analysis, which can slow down workflows for non-specialists.