Coverage-Guided Fuzzing
What is Coverage-Guided Fuzzing?
Coverage-Guided FuzzingA fuzzing technique that instruments the target to measure code coverage and evolves inputs that explore previously unseen paths, dramatically improving bug-finding efficiency.
Coverage-guided fuzzers instrument the target at compile time (AFL's afl-cc, LLVM's SanitizerCoverage) or via dynamic binary translation (QEMU mode), then run candidate inputs while recording which edges or basic blocks execute. Any input that reaches new coverage is added to an evolving corpus and further mutated, so over millions of executions the corpus drifts toward hard-to-reach code — the key insight that separates greybox fuzzing from blind random testing.
The approach was popularised by AFL (Michał Zalewski, 2013) and advanced by its community fork AFL++, by LLVM's in-process libFuzzer, and by Honggfuzz. Speed comes from fork servers and persistent mode (thousands of iterations per second), while sanitizers act as oracles: AddressSanitizer, UBSan and MemorySanitizer turn silent memory corruption into immediate, triageable crashes. Dictionaries and structure-aware mutators (libFuzzer with libprotobuf-mutator) help fuzzers past magic-byte and format checks.
Google's OSS-Fuzz, which runs these engines continuously against open-source code, has helped find over 13,000 vulnerabilities and more than 50,000 bugs across 1,000-plus projects. Defensive practice is to wire fuzzing into CI with a persistent seed corpus and regression tests, so every fix adds a crashing input that must never reappear.
flowchart LR
S[Seed corpus] --> M[Mutate input]
M --> R[Run instrumented target]
R --> C{New coverage?}
C -- Yes --> A[Add to corpus] --> M
C -- No --> D{Crash / sanitizer?}
D -- Yes --> T[Save and triage crash]
D -- No --> M● Examples
- 01
Compiling a C parser with AFL++ instrumentation and using afl-fuzz to grow a coverage-driven corpus.
- 02
libFuzzer using SanitizerCoverage to evolve inputs for a Rust crate.
● Frequently asked questions
What is Coverage-Guided Fuzzing?
A fuzzing technique that instruments the target to measure code coverage and evolves inputs that explore previously unseen paths, dramatically improving bug-finding efficiency. It belongs to the Application Security category of cybersecurity.
What does Coverage-Guided Fuzzing mean?
A fuzzing technique that instruments the target to measure code coverage and evolves inputs that explore previously unseen paths, dramatically improving bug-finding efficiency.
How do you defend against Coverage-Guided Fuzzing?
Defences for Coverage-Guided Fuzzing typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Coverage-Guided Fuzzing?
Common alternative names include: Greybox fuzzing, Feedback-driven fuzzing.