Fork me on GitHub

A ground-truth fuzzing benchmark suite based on real programs with real bugs.


To use Magma and its scripts, first install the dependencies:

apt-get update &&
  apt-get install -y util-linux inotify-tools git

Then clone Magma:

git clone --branch v1.2.1

From here on, you can use the captain scripts (in tools/captain) to build, start, and manage fuzz campaigns.

The captain/ script can build fuzzing images and start multiple campaigns in parallel. To configure it, the captainrc file is imported.

For instance, to run a single 24-hour AFL campaign against a Magma target (e.g., libpng), the captainrc file can be as such:

## Configuration parameters

# WORKDIR: path to directory where shared volumes will be created

# REPEAT: number of campaigns to run per program (per fuzzer)

# [WORKERS]: number of worker threads (default: CPU cores)

# [TIMEOUT]: time to run each campaign. This variable supports one-letter
# suffixes to indicate duration (s: seconds, m: minutes, h: hours, d: days)
# (default: 1m)

# [POLL]: time (in seconds) between polls (default: 5)

# [ISAN]: if set, build the benchmark with ISAN/fatal canaries (default: unset)

## Campaigns to run

# FUZZERS: an array of fuzzer names (from magma/fuzzers/*) to evaluate

# [fuzzer_TARGETS]: an array of target names (from magma/targets/*) to fuzz with
# `fuzzer` (default: all targets)

Then, execute ./ in the same directory. The workdir/log directory contains the build and run logs of the campaign. In addition, the fuzzer logs and outputs can be found in workdir/afl/libpng/libpng_read_fuzzer/0/findings.

The collected Magma instrumentation can be found in name-timestamped files inside workdir/afl/libpng/libpng_read_fuzzer/0/monitor. Timestamps are recorded in seconds since the beginning of the campaign. The contents of each monitor file are a CSV header and data row representing the global campaign bug reached and triggered counters at that timestamp. For instance, the monitor/43200 file could have the following contents:

AAH001_R, AAH001_T, AAH007_R, AAH007_T
1245, 342, 45324, 6345

This indicates that, up until the 12-hour mark, the AAH001 bug was reached 1245 times, and triggered 342 times, whereas the AAH007 bug was reached 45324 times, and triggered 6345 times.

These results can be summarized in a single JSON file by running:

tools/benchd/ workdir bugs.json

More details are available here.

Manual Builds

The captain toolset also provides scripts to manually build and start unmanaged campaigns:

cd tools/captain

# Build the docker image for AFL and a Magma target (e.g., libpng)
FUZZER=afl TARGET=libpng ./

# To start a single 24-hour fuzzing campaign, use the script
mkdir -p ./workdir
FUZZER=afl TARGET=libpng PROGRAM=libpng_read_fuzzer SHARED=./workdir POLL=5 \
  TIMEOUT=24h ./

Magma Versioning

To guarantee replicatable results across evaluations, Magma uses semantic versioning:

  1. MAJOR: A Magma release with incompatible API/toolset changes
  2. MINOR: An update to Magma that modifies targets (e.g., updates version or ref) or patches (e.g., adds/removes bugs), making evaluations not comparable across minor releases.
  3. PATCH: An update or a hotfix to the toolset or build system in a backward-compatible manner that preserves benchmark results.

The latest stable and anchored release of Magma is v1.2.1.


Magma is being continuously updated to add support for more fuzzing methods and applications. To that end, the near-future list of TODOs is the following:

  1. Add better instrumentation to collect information about bug distribution and complexity.
  2. Add more bugs and libraries.
  3. Add support for in-process fuzzers through stub functions.
  4. Improve collection method for canary statistics. Currently, bug ID is the index of the bug counters in a fixed-size shared-memory array, and the size of the array is hard-coded and needs to be manually updated as more bugs are added.

The long-term milestones of this project are:

  1. Implement an introspective system for collecting bug information, instead of in-line canaries.
  2. Set up an online continuous evaluation platform with live statistics for different fuzzers (à la oss-fuzz).
  3. Investigate seed selection methods for better seed coverage.
  4. Investigate binaries that maximize library coverage (à la FuzzGen).
  5. Add support for multithreaded libraries and make instrumentation thread-safe.
  6. Revamp the build system to make it more efficient. Currently, it could result in work being duplicated, like compiling the benchmark twice with the same compiler configuration or compiling all libraries twice just to change the MAGMA_STORAGE value (which only affects one object file).