Home

Awesome

<h1 align="center"> <img src="src/web_interface/static/FACT_smaller.png" alt="FACT logo with magnifying glass as the C" /> <br/> The Firmware Analysis and Comparison Tool (FACT) </h1> <div align="center">

codecov Codacy Badge Gitter chat CI Build Ruff License: GPL v3

</div>

Contents

Why FACT?

Firmware analysis can be used to achieve several interesting goals. Chief among those are identifying functionality, components and potential security weaknesses in black box firmware.

The Firmware Analysis and Comparison Tool (FACT) is intended to automate as much as possible of the manual firmware analysis work. FACT combines a growing set of powerful analyses to create a unified interface that brings the user from an arbitrary firmware sample to a finished analysis. Some of the key features of the FACT analysis, is that results are

Furthermore, FACT offers multiple ways of navigating and visualizing analysis results and firmware contents for easy accessibility. The main FACT interface is a html/js/css-based web Interface that can be hosted locally or shared through the network. In addition, FACT offers a REST-like HTTP API that can be explored with an integrated SwaggerUI. Some key features of the web interface are:

While FACT is maintained as a research prototype, the project is well tested, includes a baseline of documentation and offers a multitude of production level features. We're always looking for feedback and feature requests.

More details and some screenshots can be found on our project page.

Setup

Requirements

FACT is designed as a multiprocess application, the more Cores and RAM, the better.

MinimalRecommended
4 Cores16 Cores
8 GB RAM64 GB RAM
10 GB disk space10* GB disk space

[!NOTE] About 10 GB required to set up FACT code, container, and binaries. Additional space is necessary for storage of unpacked files and analysis results. This can be on a separate partition or drive.

Local Installation

It's principally possible to install FACT on any Linux distribution, but the installer is limited to

FACT requires Python 3.9–3.12 (should be the default in all distributions except Ubuntu 20.04 where you can install a newer version using apt)

The setup process is mostly automated and wrapped in a single script. Some features can be selected specifically though. For a detailed guide on how to install FACT see INSTALL.md.

[!IMPORTANT] Note that while making extensive use of containers, FACT still contains many dependencies (and there is no uninstall provided). If you want to keep your system clean, you can try one of the setup options provided in the following.

Vagrant

We provide monthly and ready-to-use vagrant boxes of our master branch. Vagrant is an easy and convenient way to get started with FACT without having to install it on your machine. Just setup vagrant and import our provided box into VirtualBox. Our boxes can be found here!

Check out on how to get started with FACT and vagrant in our tutorial.

Docker

There is also a dockerized version, but it is currently unmaintained. (see the FACT_docker repo for more information).

Usage

You can start FACT by executing the start_fact.py script. The script detects all installed components automatically.

src/start_fact.py

Afterward, FACT can be accessed on http://localhost:5000 (default) or https://localhost (if FACT is installed with nginx).

You can shut down the system by pressing <kbd>Ctrl + c</kbd> or by sending a SIGTERM to the start_fact.py script.

[!CAUTION] FACT is not intended to be used as a public internet service. The web interface is not a hardened application. We try to keep security issues limited by applying SecDevOps but FACT may still offer vulnerabilities. Make sure to reset all passwords in the fact configuration if planning to host FACT on not-fully trusted networks.

Documentation

[!TIP] More documentation on how to use FACT can be found on our wiki pages.

Our Sphinx documentation can be found here.

Information on what FACT is and how it works can also be found in the slides in the docs folder.

REST API

FACT provides a REST API. More information can be found here.

User Management

FACT provides an optional basic authentication, role, and user management. More information can be found here.

Contributing

The easiest way to contribute is writing your own plugin. Our Developer Manual can be found here.

Additional plugins

Currently available additional plugins:

Analysis Import / Export

The script src/firmware_import_export.py can be used to export unpacked files and analysis results and import them into another FACT instance. The data is stored as a ZIP archive, and this is also the format the script expects during import. To export files and analysis data of analyzed firmware images, run

python3 firmware_import_export.py export FW_UID [FW_UID_2 ...] [-o OUTPUT_DIR]

[!NOTE] The exported archives can take up significant disk space. There is no fixed relation, but it can surpass the size of the original firmware by a factor of 2 - 10.

After this, you can import the exported files with

python3 firmware_import_export.py import FW.zip [FW_2.zip ...]

Presentations

BlackHat Arsenal

We've been happy to show FACT in a number of BlackHat Arsenal sessions.

Other

Social

Acknowledgments

Thanks to @botlabsDev, who initially provided a Vagrantfile that is now, however, deprecated.

This project is partly financed by German Federal Office for Information Security (BSI) and others.

License

Firmware Analysis and Comparison Tool (FACT)

Copyright (C) 2015-2024 Fraunhofer FKIE

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program.
If not, see http://www.gnu.org/licenses/.

Some plugins may have different licenses. If so, a license file is provided in the plugin's folder.