A qualitative study identifies domain-specific usability and usefulness barriers in smart contract fuzzing tools, with a taxonomy from GitHub issues and a six-participant user study.
An Empirical Study of OSS-Fuzz Bugs
1 Pith paper cite this work. Polarity classification is still indexing.
1
Pith paper citing it
abstract
Continuous fuzzing is an increasingly popular technique for automated quality and security assurance. Google maintains OSS-Fuzz: a continuous fuzzing service for open source software. We conduct the first empirical study of OSS-Fuzz, analyzing 23,907 bugs found in 316 projects. We examine the characteristics of fuzzer-found faults, the lifecycles of such faults, and the evolution of fuzzing campaigns over time. We find that OSS-Fuzz is often effective at quickly finding bugs, and developers are often quick to patch them. However, flaky bugs, timeouts, and out of memory errors are problematic, people rarely file CVEs for security vulnerabilities, and fuzzing campaigns often exhibit punctuated equilibria, where developers might be surprised by large spikes in bugs found. Our findings have implications on future fuzzing research and practice.
citation-role summary
background 1
citation-polarity summary
fields
cs.HC 1years
2025 1verdicts
CONDITIONAL 1roles
background 1polarities
background 1representative citing papers
citing papers explorer
-
Human Side of Smart Contract Fuzzing: An Empirical Study
A qualitative study identifies domain-specific usability and usefulness barriers in smart contract fuzzing tools, with a taxonomy from GitHub issues and a six-participant user study.