Fuzzing in the Large

In the past chapters, we have always looked at fuzzing taking place on one machine for a few seconds only. In the real world, however, fuzzers are run on dozens or even thousands of machines; for hours, days and weeks; for one program or dozens of programs. In such contexts, one needs an infrastructure to collect failure data from the individual fuzzer runs, and to aggregate such data in a central repository. In this chapter, we will examine such an infrastructure, the FuzzManager framework from Mozilla.


import Fuzzer


To use the code provided in this chapter, write

>>> from fuzzingbook.FuzzingInTheLarge import <identifier>

and then make use of the following features.

The Python FuzzManager package allows for programmatic submission of failures from a large number of (fuzzed) programs. One can query crashes and their details, collect them into buckets to ensure they will be treated the same, and also retrieve coverage information for debugging both programs and their tests.

Collecting Crashes from Multiple Fuzzers

So far, all our fuzzing scenarios have been one fuzzer on one machine testing one program. Failures would be shown immediately, and diagnosed quickly by the same person who started the fuzzer. Alas, testing in the real world is different. Fuzzing is still fully automated; but now, we are talking about multiple fuzzers running on multiple machines testing multiple programs (and versions thereof), producing multiple failures that have to be handled by multiple people. This raises the question of how to manage all these activities and their interplay.

A common means to coordinate several fuzzers is to have a central repository that collects all crashes as well as their crash information. Whenever a fuzzer detects a failure, it connects via the network to a crash server, which then stores the crash information in a database.

Crash Database Crash Database Fuzzer 1 Fuzzer 1 Crash Server Crash Server Fuzzer 1->Crash Server Crash Server->Crash Database Fuzzer 2 Fuzzer 2 Fuzzer 2->Crash Server Fuzzer 3 Fuzzer 3 Fuzzer 3->Crash Server Fuzzer 4 Fuzzer 4 Fuzzer 4->Crash Server Fuzzer 5 Fuzzer 5 Fuzzer 5->Crash Server Fuzzer 6 Fuzzer 6 Fuzzer 6->Crash Server

The resulting crash database can be queried to find out which failures have occurred – typically, using a Web interface. It can also be integrated with other process activities. Most importantly, entries in the crash database can be linked to the bug database, and vice versa, such that bugs (= crashes) can be assigned to individual developers.

In such an infrastructure, collecting crashes is not limited to fuzzers. Crashes and failures occurring in the wild can also be automatically reported to the crash server. In industry, it is not uncommon to have crash databases collecting thousands of crashes from production runs – especially if the software in question is used by millions of people every day.

What information is stored in such a database?

  • Most important is the identifier of the product – that is, the product name, version information as well as the platform and the operating system. Without this information, there is no way developers can tell whether the bug is still around in the latest version, or whether it already has been fixed.

  • For debugging, the most helpful information for developers are the steps to reproduce – in a fuzzing scenario, this would be the input to the program in question. (In a production scenario, the user's input is not collected for obvious privacy reasons.)

  • Second most helpful for debugging is a stack trace such that developers can inspect which internal functionality was active in the moment of the failure. A coverage map also comes in handy, since developers can query which functions were executed and which were not.

  • If general failures are collected, developers also need to know what the expected behavior was; for crashes, this is simple, as users do not expect their software to crash.

All of this information can be collected automatically if the fuzzer (or the program in question) is set up accordingly.

In this chapter, we will explore a platform that automates all these steps. The FuzzManager platform allows to

  1. collect failure data from failing runs,
  2. enter this data into a centralized server, and
  3. query the server via a Web interface.

In this chapter, we will show how to conduct basic steps with FuzzManager, including crash submission and triage as well as coverage measurement tasks.

Running a Crash Server

FuzzManager is a tool chain for managing large-scale fuzzing processes. It is modular in the sense that you can make use of those parts you need; it is versatile in the sense that it does not impose a particular process. It consists of a server whose task is to collect crash data, as well as of various collector utilities that collect crash data to send it to the server.

Setting up the Server

To run the examples in this notebook, we need to run a crash server – that is, the FuzzManager server. You can either

  1. Run your own server. To do so, you need to follow the installation steps listed under "Server Setup" on the FuzzManager page. The FuzzManager folder should be created in the same folder as this notebook.

  2. Have the notebook start (and stop) a server. The following commands following commands do this automatically. They are meant for the purposes of this notebook only, though; if you want to experiment with your own server, run it manually, as described above.

import os
import sys
import shutil

We start with getting the fresh server code from the repository.

if os.path.exists('FuzzManager'):

The base repository is https://github.com/MozillaSecurity/FuzzManager, but we use the uds-se repository as this repository has the 0.4.1 stable release of FuzzManager.

!git clone https://github.com/uds-se/FuzzManager
Cloning into 'FuzzManager'...
remote: Enumerating objects: 11755, done.
remote: Counting objects: 100% (11755/11755), done.
remote: Compressing objects: 100% (3726/3726), done.
remote: Total 11755 (delta 7943), reused 11674 (delta 7862), pack-reused 0
Receiving objects: 100% (11755/11755), 5.33 MiB | 3.53 MiB/s, done.
Resolving deltas: 100% (7943/7943), done.
DEPRECATION: celery 4.2.2 has a non-standard dependency specifier pytz>dev. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of celery or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063

[notice] A new release of pip is available: 23.3.2 -> 24.0
[notice] To update, run: pip install --upgrade pip
!cd FuzzManager; {sys.executable} server/manage.py migrate > /dev/null

We create a user named demo with a password demo, using this handy trick.

!(cd FuzzManager; echo "from django.contrib.auth import get_user_model; User = get_user_model(); User.objects.create_superuser('demo', 'demo@fuzzingbook.org', 'demo')" | {sys.executable} server/manage.py shell)

We create a token for this user. This token will later be used by automatic commands for authentication.

import subprocess
import sys
result = subprocess.run(['python', 

err = result.stderr.decode('ascii')
if len(err) > 0:
    print(err, file=sys.stderr, end="")
token = result.stdout
token = token.decode('ascii').strip()

The token is stored in ~/.fuzzmanagerconf in our home folder. This is the full configuration:

sigdir = /home/example/fuzzingbook
serverhost =
serverport = 8000
serverproto = http
serverauthtoken = 99ba0244a16c3575c036435a43e5246aa8607969
tool = fuzzingbook
Starting the Server

Once the server is set up, we can start it. On the command line, we use

$ cd FuzzManager; python server/manage.py runserver

In our notebook, we can do this programmatically, using the Process framework introduced for fuzzing Web servers. We let the FuzzManager server run in its own process, which we start in the background.

For multiprocessing, we use the multiprocess module - a variant of the standard Python multiprocessing module that also works in notebooks. If you are running this code outside a notebook, you can also use multiprocessing instead.

from multiprocess import Process
import subprocess
def run_fuzzmanager():
    def run_fuzzmanager_forever():
        proc = subprocess.Popen(['python', 'server/manage.py',

        while True:
            line = proc.stdout.readline()
            print(line, end='')

    fuzzmanager_process = Process(target=run_fuzzmanager_forever)

    return fuzzmanager_process

While the server is running, you will be able to see its output below.

fuzzmanager_process = run_fuzzmanager()
import time
# wait a bit after interactions

Logging In

Now that the server is up and running, FuzzManager can be reached on the local host using this URL.

fuzzmanager_url = ""

To log in, use the username demo and the password demo. In this notebook, we do this programmatically, using the Selenium interface introduced in the chapter on GUI fuzzing.

from IPython.display import display, Image
from bookutils import HTML, rich_output
from GUIFuzzer import start_webdriver  # minor dependency

For an interactive session, set headless to False; then you can interact with FuzzManager at the same time you are interacting with this notebook.

gui_driver = start_webdriver(headless=True, zoom=1.2)
gui_driver.set_window_size(1400, 600)

This is the starting screen of FuzzManager:

We now log in by sending demo both as username and password, and then click on the Login button.

After login, we find an empty database. This is where crashes will appear, once we have collected them.

Collecting Crashes

To fill our database, we need some crashes. Let us take a look at simply-buggy, an example repository containing trivial C++ programs for illustration purposes.

!git clone https://github.com/uds-se/simply-buggy
Cloning into 'simply-buggy'...
remote: Enumerating objects: 22, done.
remote: Total 22 (delta 0), reused 0 (delta 0), pack-reused 22
Receiving objects: 100% (22/22), 4.90 KiB | 2.45 MiB/s, done.
Resolving deltas: 100% (9/9), done.

The make command compiles our target program, including our first target, the simple-crash example. Alongside the program, there is also a configuration file generated.

!(cd simply-buggy && make)
clang++ -fsanitize=address -g -o maze maze.cpp
clang++ -fsanitize=address -g -o out-of-bounds out-of-bounds.cpp
clang++ -fsanitize=address -g -o simple-crash simple-crash.cpp

Let's take a look at the simple-crash source code in simple-crash.cpp. As you can see, the source code is fairly simple: A forced crash by writing to a (near)-NULL pointer. This should immediately crash on most machines.

 * simple-crash - A simple NULL crash.
 * WARNING: This program neither makes sense nor should you code like it is
 *          done in this program. It is purely for demo purposes and uses
 *          bad and meaningless coding habits on purpose.

int crash() {
  int* p = (int*)0x1;
  *p = 0xDEADBEEF;
  return *p;

int main(int argc, char** argv) {
  return crash();

The configuration file simple-crash.fuzzmanagerconf generated for the the binary also contains some straightforward information, like the version of the program and other metadata that is required or at least useful later on when submitting crashes.

platform = x86-64
product = simple-crash-simple-crash
product_version = 83038f74e812529d0fc172a718946fbec385403e
os = linux

pathPrefix = /Users/zeller/Projects/fuzzingbook/notebooks/simply-buggy/
buildFlags = -fsanitize=address -g

Let us run the program! We immediately get a crash trace as expected:

==66666==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x00010062fe0c bp 0x00016f7d26a0 sp 0x00016f7d2660 T0)
==66666==The signal is caused by a WRITE memory access.
==66666==Hint: address points to the zero page.
    #0 0x10062fe0c in crash() simple-crash.cpp:11
    #1 0x10062fe94 in main simple-crash.cpp:16
    #2 0x18d5920dc  (<unknown module>)

==66666==Register values:
 x[0] = 0x0000000000000001   x[1] = 0x000000016f7d2918   x[2] = 0x000000016f7d2928   x[3] = 0x000000016f7d2c50  
 x[4] = 0x000000018d5b8ac8   x[5] = 0x00000001fa157ad8   x[6] = 0x0000000000000000   x[7] = 0x0000000000000db0  
 x[8] = 0x0000007000020000   x[9] = 0x00000000deadbeef  x[10] = 0x0000000000000001  x[11] = 0x00000000000002c0  
x[12] = 0x0000000000008000  x[13] = 0x1000000000000000  x[14] = 0x0000000000000004  x[15] = 0x0000000000008000  
x[16] = 0x000000016f7d26e0  x[17] = 0x000000016f7d26e0  x[18] = 0x0000000000000000  x[19] = 0x0000000100a3dbf0  
x[20] = 0x000000010062fe7c  x[21] = 0x000000016f7d26e0  x[22] = 0x0000000100a3d910  x[23] = 0x000000016f7d2760  
x[24] = 0x000000016f7d27a0  x[25] = 0x000000018d6062db  x[26] = 0x0000000000000000  x[27] = 0x0000000000000000  
x[28] = 0x0000000000000000     fp = 0x000000016f7d26a0     lr = 0x000000010062fe98     sp = 0x000000016f7d2660  
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV simple-crash.cpp:11 in crash()

Now, what we would actually like to do is to run this binary from Python instead, detect that it crashed, collect the trace and submit it to the server. Let's start with a simple script that would just run the program we give it and detect the presence of the ASan trace:

import subprocess
cmd = ["simply-buggy/simple-crash"]
result = subprocess.run(cmd, stderr=subprocess.PIPE)
stderr = result.stderr.decode().splitlines()
crashed = False

for line in stderr:
    if "ERROR: AddressSanitizer" in line:
        crashed = True

if crashed:
    print("Yay, we crashed!")
    print("Move along, nothing to see...")
Yay, we crashed!

With this script, we can now run the binary and indeed detect that it crashed. But how do we send this information to the crash server now? Let's add a few features from the FuzzManager toolbox.

Program Configurations

A ProgramConfiguration is largely a container class storing various properties of the program, e.g. product name, the platform, version and runtime options. By default, it reads the information from the .fuzzmanagerconf file created for the program under test.

from FTB.ProgramConfiguration import ProgramConfiguration
configuration = ProgramConfiguration.fromBinary('simply-buggy/simple-crash')
(configuration.product, configuration.platform)
('simple-crash-simple-crash', 'x86-64')

Crash Info

A CrashInfo object stores all the necessary data about a crash, including

  • the stdout output of your program
  • the stderr output of your program
  • crash information as produced by GDB or AddressSanitizer
  • a ProgramConfiguration instance
from FTB.Signatures.CrashInfo import CrashInfo

Let's collect the information for the run of simply-crash:

cmd = ["simply-buggy/simple-crash"]
result = subprocess.run(cmd, stderr=subprocess.PIPE, stdout=subprocess.PIPE)
stderr = result.stderr.decode().splitlines()
 '==66680==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x00010033fe0c bp 0x00016fac2740 sp 0x00016fac2700 T0)']
stdout = result.stdout.decode().splitlines()

This reads and parses our ASan trace into a more generic format, returning us a generic CrashInfo object that we can inspect and/or submit to the server:

crashInfo = CrashInfo.fromRawCrashData(stdout, stderr, configuration)
Crash trace:

# 00    crash
# 01    main
# 02    <unknow

Crash address: 0x1

Last 5 lines on stderr:
x[24] = 0x000000016fac2840  x[25] = 0x000000018d6062db  x[26] = 0x0000000000000000  x[27] = 0x0000000000000000  
x[28] = 0x0000000000000000     fp = 0x000000016fac2740     lr = 0x000000010033fe98     sp = 0x000000016fac2700  
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV simple-crash.cpp:11 in crash()


The last step is to send the crash info to our crash manager. A Collector is a feature to communicate with a CrashManager server. Collector provides an easy client interface that allows your clients to submit crashes as well as download and match existing signatures to avoid reporting frequent issues repeatedly.

from Collector.Collector import Collector

We instantiate the collector instance; this will be our entry point for talking to the server.

collector = Collector()

To submit the crash info, we use the collector's submit() method:

{'rawStdout': '',
 'rawStderr': 'AddressSanitizer:DEADLYSIGNAL\n=================================================================\n==66680==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x00010033fe0c bp 0x00016fac2740 sp 0x00016fac2700 T0)\n==66680==The signal is caused by a WRITE memory access.\n==66680==Hint: address points to the zero page.\n    #0 0x10033fe0c in crash() simple-crash.cpp:11\n    #1 0x10033fe94 in main simple-crash.cpp:16\n    #2 0x18d5920dc  (<unknown module>)\n\n==66680==Register values:\n x[0] = 0x0000000000000001   x[1] = 0x000000016fac29b0   x[2] = 0x000000016fac29c0   x[3] = 0x000000016fac2cd8  \n x[4] = 0x000000018d5b8ac8   x[5] = 0x00000001fa157ad8   x[6] = 0x0000000000000000   x[7] = 0x0000000000000db0  \n x[8] = 0x0000007000020000   x[9] = 0x00000000deadbeef  x[10] = 0x0000000000000001  x[11] = 0x00000000000002c0  \nx[12] = 0x0000000000008000  x[13] = 0x1000000000000000  x[14] = 0x0000000000000004  x[15] = 0x0000000000008000  \nx[16] = 0x000000016fac2780  x[17] = 0x000000016fac2780  x[18] = 0x0000000000000000  x[19] = 0x000000010074dbf0  \nx[20] = 0x000000010033fe7c  x[21] = 0x000000016fac2780  x[22] = 0x000000010074d910  x[23] = 0x000000016fac2800  \nx[24] = 0x000000016fac2840  x[25] = 0x000000018d6062db  x[26] = 0x0000000000000000  x[27] = 0x0000000000000000  \nx[28] = 0x0000000000000000     fp = 0x000000016fac2740     lr = 0x000000010033fe98     sp = 0x000000016fac2700  \nAddressSanitizer can not provide additional info.\nSUMMARY: AddressSanitizer: SEGV simple-crash.cpp:11 in crash()\n==66680==ABORTING',
 'rawCrashData': '',
 'metadata': '{"pathPrefix": "/Users/zeller/Projects/fuzzingbook/notebooks/simply-buggy/", "buildFlags": "-fsanitize=address -g"}',
 'testcase_size': 0,
 'testcase_quality': 0,
 'testcase_isbinary': False,
 'platform': 'x86-64',
 'product': 'simple-crash-simple-crash',
 'product_version': '83038f74e812529d0fc172a718946fbec385403e',
 'os': 'linux',
 'client': 'Braeburn.fritz.box',
 'tool': 'fuzzingbook',
 'env': '',
 'args': '',
 'bucket': None,
 'id': 1,
 'shortSignature': '[@ crash]',
 'crashAddress': '0x1'}

Inspecting Crashes

We now submitted something to our local FuzzManager demo instance. If you run the crash server on your local machine, you can go to you should see the crash info just submitted. You can inquire the product, version, operating system, and further crash details.

If you click on the crash ID, you can further inspect the submitted data.

Since Collectors can be called from any program (provided they are configured to talk to the correct server), you can now collect crashes from anywhere – fuzzers on remote machines, crashes occurring during beta testing, or even crashes during production.

Crash Buckets

One challenge with collecting crashes is that the same crashes occur multiple times. If a product is in the hands of millions of users, chances are that thousands of them will encounter the same bug, and thus the same crash. Therefore, the database will have thousands of entries that are all caused by the same one bug. Therefore, it is necessary to identify those failures that are similar and to group them together in a set called a crash bucket or bucket for short.

In FuzzManager, a bucket is defined through a crash signature, a list of predicates matching a set of bugs. Such a predicate can refer to a number of features, the most important being

  • the current program counter, reporting the instruction executed at the moment of the crash;
  • elements from the stack trace, showing which functions were active at the moment of the crash.

We can create such a signature right away when viewing a single crash:

Clicking the red Create button creates a bucket for this crash. A crash signature will be proposed to you for matching this and future crashes of the same type:

Accept it by clicking Save.

You will be redirected to the newly created bucket, which shows you the size (how many crashes it holds), its bug report status (buckets can be linked to bugs in an external bug tracker like Bugzilla) and many other useful information.

Crash Signatures

If you click on the Signatures entry in the top menu, you should also see your newly created entry.