The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
Existing Greybox Fuzzers (GF) cannot be effectively directed, for instance, towards problematic changes or patches, towards critical system calls or dangerous locations, or towards functions in the stack-trace of a reported vulnerability that we wish to reproduce. In this paper, we introduce Directed Greybox Fuzzing (DGF) which generates inputs with the objective of reaching a given set of target program locations efficiently. We develop and evaluate a simulated annealing-based power schedule that gradually assigns more energy to seeds that are closer to the target locations while reducing energy for seeds that are further away. Experiments with our implementation AFLGo demonstrate that DGF outperforms both directed symbolic-execution-based whitebox fuzzing and undirected greybox fuzzing. We show applications of DGF to patch testing and crash reproduction, and discuss the integration of AFLGo into Google's continuous fuzzing platform OSS-Fuzz. Due to its directedness, AFLGo could find 39 bugs in several well-fuzzed, security-critical projects like LibXML2. 17 CVEs were assigned.
How it got here
How it got here
agent via openalex
Added
2026-10-24 22:09 UTC
Not denied by
a person 2026-10-29 17:12 UTC
Cite it as
@misc{bohme2017directed,
title = {Directed Greybox Fuzzing},
author = {Marcel Böhme and Van-Thuan Pham and Manh-Dung Nguyen and Abhik Roychoudhury},
year = {2017},
journal = {ACM SIGSAC Conference on Computer and Communications Security (CCS)},
pages = {2329--2344},
doi = {10.1145/3133956.3134020},
}