SoK: Prudent Evaluation Practices for Fuzzing
Not on the map. Why?
Abstract (arXiv)
Fuzzing has proven to be a highly effective approach to uncover software bugs over the past decade. After AFL popularized the groundbreaking concept of lightweight coverage feedback, the field of fuzzing has seen a vast amount of scientific work proposing new techniques, improving methodological aspects of existing strategies, or porting existing methods to new domains. All such work must demonstrate its merit by showing its applicability to a problem, measuring its performance, and often showing its superiority over existing works in a thorough, empirical evaluation. Yet, fuzzing is highly sensitive to its target, environment, and circumstances, e.g., randomness in the testing process. After all, relying on randomness is one of the core principles of fuzzing, governing many aspects of a fuzzer's behavior. Combined with the often highly difficult to control environment, the reproducibility of experiments is a crucial concern and requires a prudent evaluation setup. To address these threats to validity, several works, most notably Evaluating Fuzz Testing by Klees et al., have outlined how a carefully designed evaluation setup should be implemented, but it remains unknown to what extent their recommendations have been adopted in practice. In this work, we systematically analyze the evaluation of 150 fuzzing papers published at the top venues between 2018 and 2023. We study how existing guidelines are implemented and observe potential shortcomings and pitfalls. We find a surprising disregard of the existing guidelines regarding statistical tests and systematic errors in fuzzing evaluations. For example, when investigating reported bugs, ...
Key facts. Cited by 8 papers in the map (data through 14 Oct 2026). First posted on arXiv 16 May 2024.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2024: 2; 2025: 3; 2026: 3.
8 papers.
- 2026ARVO: Atlas of Reproducible Vulnerabilities for Open-Source Softwarecited by 9
- 2026SoK: The Pitfalls of Deep Reinforcement Learning for Cybersecuritycited by 4
- 2024ARVO: Atlas of Reproducible Vulnerabilities for Open-Source Softwarecited by 2
- 2025SeedAIchemy: LLM-Driven Seed Corpus Generation for Fuzzingcited by 1
- 2024Direction for Detection: A Survey of Automated Vulnerability Detection and all of its Pain Pointscited by 0
- 2025Orion: Fuzzing Workflow Automationcited by 0
- 2025Clutch Control: An Attention-based Combinatorial Bandit for Efficient Mutation in JavaScript Engine Fuzzingcited by 0
- 2026CAROL: Context-Aware Online Learning for Fuzzer Schedulingcited by 0
- 2026CAROL: Context-Aware Online Learning for Fuzzer Scheduling6 Sep 2026
- 2026ARVO: Atlas of Reproducible Vulnerabilities for Open-Source Software15 Jun 2026
- 2026SoK: The Pitfalls of Deep Reinforcement Learning for Cybersecurity9 Feb 2026
- 2025SeedAIchemy: LLM-Driven Seed Corpus Generation for Fuzzing16 Nov 2025
- 2025Clutch Control: An Attention-based Combinatorial Bandit for Efficient Mutation in JavaScript Engine Fuzzing14 Oct 2025
- 2025Orion: Fuzzing Workflow Automation18 Sep 2025
- 2024Direction for Detection: A Survey of Automated Vulnerability Detection and all of its Pain Points15 Dec 2024
- 2024ARVO: Atlas of Reproducible Vulnerabilities for Open-Source Software4 Aug 2024