Aflpp

AFL++

AFL++ is a fork of the original AFL fuzzer that offers better fuzzing performance and more advanced features while maintaining stability. A major benefit over libFuzzer is that AFL++ has stable support for running fuzzing campaigns on multiple cores, making it ideal for large-scale fuzzing efforts.

When to Use

Choose AFL++ when:

• You need multi-core fuzzing to maximize throughput
• Your project can be compiled with Clang or GCC
• You want diverse mutation strategies and mature tooling
• libFuzzer has plateaued and you need more coverage
• You're fuzzing production codebases that benefit from parallel execution

Quick Start

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {    // Call your code with fuzzer-provided data    check_buf((char*)data, size);    return 0;}

Compile and run:

# Setup AFL++ wrapper script first (see Installation)./afl++ docker afl-clang-fast++ -DNO_MAIN=1 -O2 -fsanitize=fuzzer harness.cc main.cc -o fuzzmkdir seeds && echo "aaaa" > seeds/minimal_seed./afl++ docker afl-fuzz -i seeds -o out -- ./fuzz

Installation

AFL++ has many dependencies including LLVM, Python, and Rust. We recommend using a current Debian or Ubuntu distribution for fuzzing with AFL++.

Ubuntu/Debian

Prior to installing afl++, check the clang version dependency of the packge with apt-cache show afl++, and install the matching lld version (e.g., lld-17).

apt install afl++ lld-17

Docker (from Docker Hub)

docker pull aflplusplus/aflplusplus:stable

Docker (from source)

git clone --depth 1 --branch stable https://github.com/AFLplusplus/AFLpluspluscd AFLplusplusdocker build -t aflplusplus .

From source

Refer to the Dockerfile for Ubuntu version requirements and dependencies. Set LLVM_CONFIG to specify Clang version (e.g., llvm-config-18).

Wrapper Script Setup

Create a wrapper script to run AFL++ on host or Docker:

cat <<'EOF' > ./afl++#!/bin/shAFL_VERSION="${AFL_VERSION:-"stable"}"case "$1" in   host)        shift        bash -c "$*"        ;;    docker)        shift        /usr/bin/env docker run -i \            --privileged \            -v ./:/src \            --rm \            --name "afl_fuzzing_$$" \            "aflplusplus/aflplusplus:$AFL_VERSION" \            bash -c "cd /src && bash -c \"$*\""        ;;    *)        echo "Usage: $0 {host|docker}"        exit 1        ;;esacEOFchmod +x ./afl++

The examples below use docker mode, apart from the system configuration commands that have to reach the host kernel. Swap in host to run any of them against an AFL++ installed on the machine itself. The wrapper joins everything after the mode argument into a single shell string, so quoting does not survive: an argument containing a space (-x "my dict.dict") arrives word-split. Rename such files without spaces, or edit the wrapper for that run.

The missing -t is deliberate. docker run -ti aborts with the input device is not a TTY whenever stdin is not a terminal, which covers CI jobs and anything an agent or script drives. afl-fuzz notices there is no terminal and prints plain status lines in place of the full-screen UI. A program that insists on a terminal, such as watch, has to run on the host side of the wrapper instead. $$ expands to the wrapper's PID, so parallel instances get distinct container names rather than colliding on a single afl_fuzzing. docker ps truncates the COMMAND column, so every row looks alike; use docker ps --no-trunc to tell the instances apart before stopping one.

Security Warning: The afl-system-config and afl-persistent-config scripts require root privileges and disable OS security features. Do not fuzz on production systems or your development environment. Use a dedicated VM instead.

System Configuration

Run after each reboot for up to 15% more executions per second:

./afl++ host afl-system-config

afl-system-config tunes the kernel it runs against, so run it on the machine that hosts the campaign. ./afl++ docker afl-system-config reaches the same settings through the wrapper's --privileged container, which is the only route when AFL++ is installed via Docker alone.

For maximum performance, disable kernel security mitigations (requires grub bootloader, not supported in Docker):

./afl++ host afl-persistent-configupdate-grubreboot./afl++ host afl-system-config

Verify with cat /proc/cmdline - output should include mitigations=off.

Writing a Harness

Harness Structure

AFL++ supports libFuzzer-style harnesses:

#include <stdint.h>#include <stddef.h>
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {    // 1. Validate input size if needed    if (size < MIN_SIZE || size > MAX_SIZE) return 0;
    // 2. Call target function with fuzz data    target_function(data, size);
    // 3. Return 0 (non-zero reserved for future use)    return 0;}

Harness Rules

See Also: For detailed harness writing techniques, patterns for handling complex inputs, and advanced strategies, see the fuzz-harness-writing technique skill.

Compilation

AFL++ offers multiple compilation modes with different trade-offs.

Compilation Mode Decision Tree

Choose your compilation mode:

• LTO mode (afl-clang-lto): Best performance and instrumentation. Try this first.
• LLVM mode (afl-clang-fast): Fall back if LTO fails to compile.
• GCC plugin (afl-gcc-fast): For projects requiring GCC.

Basic Compilation (LLVM mode)

./afl++ docker afl-clang-fast++ -DNO_MAIN=1 -O2 -fsanitize=fuzzer harness.cc main.cc -o fuzz

GCC Compilation

./afl++ docker afl-g++-fast -DNO_MAIN=1 -O2 -fsanitize=fuzzer harness.cc main.cc -o fuzz

Important: GCC version must match the version used to compile the AFL++ GCC plugin.

With Sanitizers

./afl++ docker AFL_USE_ASAN=1 afl-clang-fast++ -DNO_MAIN=1 -O2 -fsanitize=fuzzer harness.cc main.cc -o fuzz

See Also: For detailed sanitizer configuration, common issues, and advanced flags, see the address-sanitizer and undefined-behavior-sanitizer technique skills.

Build Flags

Note that -g is not necessary, it is added by default by the AFL++ compilers.

Corpus Management

Creating Initial Corpus

AFL++ requires at least one non-empty seed file:

mkdir seedsecho "aaaa" > seeds/minimal_seed

For real projects, gather representative inputs:

• Download example files for the format you're fuzzing
• Extract test cases from the project's test suite
• Use minimal valid inputs for your file format

Corpus Minimization

After a campaign, minimize the corpus to keep only unique coverage:

./afl++ docker afl-cmin -i out/default/queue -o minimized_corpus -- ./fuzz

See Also: For corpus creation strategies, dictionaries, and seed selection, see the fuzzing-corpus technique skill.

Running Campaigns

Basic Run

./afl++ docker afl-fuzz -i seeds -o out -- ./fuzz

Setting Environment Variables

./afl++ docker AFL_FAST_CAL=1 afl-fuzz -i seeds -o out -- ./fuzz

Interpreting Output

AFL++ reports these statistics either way, but how you read them depends on the mode. The wrapper's docker run -i gives the container no TTY, so afl-fuzz drops the full-screen UI and writes plain status lines to the log instead — the fields below appear there, and in state/<instance>/fuzzer_stats. To get the interactive UI, run host mode in a terminal, or add -t to the wrapper for a run you are watching by hand.

Output Directory Structure

out/default/├── cmdline          # How was the SUT invoked?├── crashes/         # Inputs that crash the SUT│   └── id:000000,sig:06,src:000002,time:286,execs:13105,op:havoc,rep:4├── hangs/           # Inputs that hang the SUT├── queue/           # Test cases reproducing final fuzzer state│   ├── id:000000,time:0,execs:0,orig:minimal_seed│   └── id:000001,src:000000,time:0,execs:8,op:havoc,rep:6,+cov├── fuzzer_stats     # Campaign statistics└── plot_data        # Data for plotting

Analyzing Results

View live campaign statistics:

./afl++ docker afl-whatsup out

Create coverage plots. The aflplusplus image already ships gnuplot-nox; in host mode, install gnuplot first with apt install gnuplot.

./afl++ docker afl-plot out/default out_graph/

Re-executing Test Cases

Pass one of the filenames from out/default/crashes/:

./afl++ docker ./fuzz out/default/crashes/id:000000,sig:06,src:000002,time:286,execs:13105,op:havoc,rep:4

Fuzzer Options

Environment Variables That Matter

AFL++ has many environment variables, but most are niche. These are the ones that matter in practice.

Always Set These

# Every campaign should use tmpfs — SSDs will thank you, and it's fasterAFL_TMPDIR=/dev/shm

AFL_TMPDIR is a free performance win with no downsides — not setting it wears out your SSD and slows fuzzing.

Slow Targets

# Speeds up calibration ~2.5x — use when targets are slow (e.g., >10 ms/exec)AFL_FAST_CAL=1

AFL_FAST_CAL reduces calibration time with negligible precision loss. Recommended specifically for slow targets where calibration would otherwise take a long time.

Multi-Core Campaigns

# On the primary (-M) instance only — needed for afl-cmin, not for fuzzing itselfAFL_FINAL_SYNC=1
# On all instances — cache test cases in memory (default: 50 MB, good range: 50-250 MB)AFL_TESTCACHE_SIZE=100

AFL_FINAL_SYNC tells the primary instance to do a final import from all secondaries when stopping. This does not affect the fuzzing process itself — it only matters when you later run afl-cmin for corpus minimization, ensuring the primary's queue has the full combined corpus. AFL_TESTCACHE_SIZE caches test cases in memory to reduce disk I/O; the default is 50 MB and values between 50-250 MB work well for most campaigns.

CI/Automated Fuzzing

# Fail fast if fuzzing isn't finding anythingAFL_EXIT_ON_TIME=3600  # 1 hour with no new paths = stop
# Or run until "done" (all queue entries processed)AFL_EXIT_WHEN_DONE=1
# Headless environmentsAFL_NO_UI=1

Unbounded fuzzing in CI wastes resources. Set time limits or use exit conditions.

Variables to Avoid

Multi-Core Fuzzing

AFL++ excels at multi-core fuzzing with two major advantages:

1. More executions per second (scales linearly with physical cores)
2. Asymmetrical fuzzing (e.g., one ASan job, rest without sanitizers)

Starting a Campaign

Start the primary fuzzer (in background):

./afl++ docker afl-fuzz -M primary -i seeds -o state -- ./fuzz 1>primary.log 2>primary.error </dev/null &

Start secondary fuzzers (as many as you have cores):

./afl++ docker afl-fuzz -S secondary01 -i seeds -o state -- ./fuzz 1>secondary01.log 2>secondary01.error </dev/null &./afl++ docker afl-fuzz -S secondary02 -i seeds -o state -- ./fuzz 1>secondary02.log 2>secondary02.error </dev/null &

The </dev/null is required, not decorative. docker run -i keeps the client reading its own stdin, and a backgrounded process that reads the terminal is sent SIGTTIN, whose default action stops it — so without the redirect these jobs show up as Stopped in jobs and never fuzz.

Monitoring Multi-Core Campaigns

List all running jobs:

jobs

View live statistics. watch needs a terminal that docker run -i does not give it, so wrap the whole invocation instead of running watch inside the container. Every tick starts a container, which is why the interval is 5 seconds rather than 1:

watch -n5 --color ./afl++ docker afl-whatsup state/

Stopping All Fuzzers

kill $(jobs -p)

Coverage Analysis

AFL++ automatically tracks coverage through edge instrumentation. Coverage information is stored in fuzzer_stats and plot_data.

Measuring Coverage

Use afl-plot to visualize coverage over time:

./afl++ docker afl-plot out/default out_graph/

Improving Coverage

• Use dictionaries for format-aware fuzzing
• Run longer campaigns (cycles_wo_finds indicates plateau)
• Try different mutation strategies with multi-core fuzzing
• Analyze coverage gaps and add targeted seed inputs

See Also: For detailed coverage analysis techniques, identifying coverage gaps, and systematic coverage improvement, see the coverage-analysis technique skill.

CMPLOG

CMPLOG/RedQueen is the best path constraint solving mechanism available in any fuzzer. To enable it, the fuzz target needs to be instrumented for it. Before building the fuzzing target set the environment variable:

./afl++ docker AFL_LLVM_CMPLOG=1 make

No special action is needed for compiling and linking the harness.

To run a fuzzer instance with a CMPLOG instrumented fuzzing target, add -c0 to the command like arguments:

./afl++ docker afl-fuzz -c0 -S cmplog -i seeds -o state -- ./fuzz 1>cmplog.log 2>cmplog.error </dev/null &

Sanitizer Integration

Sanitizers are essential for finding memory corruption bugs that don't cause immediate crashes.

AddressSanitizer (ASan)

./afl++ docker AFL_USE_ASAN=1 afl-clang-fast++ -DNO_MAIN=1 -O2 -fsanitize=fuzzer harness.cc main.cc -o fuzz

Note: Memory limit (-m) is not supported with ASan due to 20TB virtual memory reservation.

UndefinedBehaviorSanitizer (UBSan)

./afl++ docker AFL_USE_UBSAN=1 afl-clang-fast++ -DNO_MAIN=1 -O2 -fsanitize=fuzzer,undefined harness.cc main.cc -o fuzz

Common Sanitizer Issues

See Also: For comprehensive sanitizer configuration and troubleshooting, see the address-sanitizer technique skill.

Advanced Usage

Tips and Tricks

Standard Input Fuzzing

AFL++ can fuzz programs reading from stdin without a libFuzzer harness:

./afl++ docker afl-clang-fast++ -O2 main_stdin.c -o fuzz_stdin./afl++ docker afl-fuzz -i seeds -o out -- ./fuzz_stdin

This is slower than persistent mode but requires no harness code.

File Input Fuzzing

For programs that read files, use @@ placeholder:

./afl++ docker afl-clang-fast++ -O2 main_file.c -o fuzz_file./afl++ docker afl-fuzz -i seeds -o out -- ./fuzz_file @@

For better performance, use fmemopen to create file descriptors from memory.

Argument Fuzzing

Fuzz command-line arguments using argv-fuzz-inl.h:

#include <stdio.h>#include <stdlib.h>#include <string.h>
#ifdef __AFL_COMPILER#include "argv-fuzz-inl.h"#endif
void check_buf(char *buf, size_t buf_len) {    if(buf_len > 0 && buf[0] == 'a') {        if(buf_len > 1 && buf[1] == 'b') {            if(buf_len > 2 && buf[2] == 'c') {                abort();            }        }    }}
int main(int argc, char *argv[]) {#ifdef __AFL_COMPILER    AFL_INIT_ARGV();#endif
    if (argc < 2) {        fprintf(stderr, "Usage: %s <input_string>\n", argv[0]);        return 1;    }
    char *input_buf = argv[1];    size_t len = strlen(input_buf);    check_buf(input_buf, len);    return 0;}

Download the header:

curl -O https://raw.githubusercontent.com/AFLplusplus/AFLplusplus/stable/utils/argv_fuzzing/argv-fuzz-inl.h

Compile and run:

./afl++ docker afl-clang-fast++ -O2 main_arg.c -o fuzz_arg./afl++ docker afl-fuzz -i seeds -o out -- ./fuzz_arg

Performance Tuning

Troubleshooting

Related Skills

Technique Skills

Related Fuzzers

Resources

Key External Resources

AFL++ GitHub Repository Official repository with comprehensive documentation, examples, and issue tracker.

Fuzzing in Depth Advanced documentation by the AFL++ team covering instrumentation modes, optimization techniques, and advanced use cases.

AFL++ Under The Hood Technical deep-dive into AFL++ internals, mutation strategies, and coverage tracking mechanisms.

AFL++: Combining Incremental Steps of Fuzzing Research Research paper describing AFL++ architecture and performance improvements over original AFL.

Video Resources

• Fuzzing cURL - Trail of Bits blog post on using AFL++ argument fuzzing for cURL
• Sudo Vulnerability Walkthrough - LiveOverflow series on rediscovering CVE-2021-3156
• Rediscovery of libpng bug - LiveOverflow video on finding CVE-2023-4863