One Fuzz Doesn't Fit All: Optimizing Directed Fuzzing via Target-tailored Program State Restriction
| dc.contributor.author | Srivastava, Prashast | en |
| dc.contributor.author | Nagy, Stefan | en |
| dc.contributor.author | Hicks, Matthew | en |
| dc.contributor.author | Bianchi, Antonio | en |
| dc.contributor.author | Payer, Mathias | en |
| dc.date.accessioned | 2023-03-07T13:25:02Z | en |
| dc.date.available | 2023-03-07T13:25:02Z | en |
| dc.date.issued | 2022-12-05 | en |
| dc.date.updated | 2023-01-23T15:13:37Z | en |
| dc.description.abstract | Fuzzing is the de-facto default technique to discover software flaws, randomly testing programs to discover crashing test cases. Yet, a particular scenario may only care about specific code regions (for, e.g., bug reproduction, patch or regression testing)—spurring the adoption of directed fuzzing. Given a set of pre-determined target locations, directed fuzzers drive exploration toward them through distance minimization strategies that (1) isolate the closest-reaching test cases and (2) mutate them stochastically. However, these strategies are applied onto every explored test case—irrespective of whether they ever reach the targets—stalling progress on the paths where targets are unreachable. Accelerating directed fuzzing requires prioritizing target-reachable paths. To overcome the bottleneck of wasteful exploration in directed fuzzing, we introduce tripwiring: a lightweight technique to preempt and terminate the fuzzing of paths that will never reach target locations. By constraining exploration to only the set of target-reachable program paths, tripwiring curtails directed fuzzers’ search noise—while unshackling them from the high-overhead instrumentation and bookkeeping of distance minimization—enabling directed fuzzers to obtain up to 99× higher test case throughput. We implement tripwiring-directed fuzzing as a prototype, Sieve- Fuzz, and evaluate it alongside the state-of-the-art directed fuzzers AFLGo, BEACON and the leading undirected fuzzer AFL++. Overall, across nine benchmarks, SieveFuzz’s tripwiring enables it to trigger bugs on an average 47% more consistently and 117% faster than AFLGo, BEACON and AFL++. | en |
| dc.description.version | Published version | en |
| dc.format.mimetype | application/pdf | en |
| dc.identifier.doi | https://doi.org/10.1145/3564625.3564643 | en |
| dc.identifier.uri | http://hdl.handle.net/10919/114049 | en |
| dc.language.iso | en | en |
| dc.publisher | ACM | en |
| dc.rights | Creative Commons Attribution 4.0 International | en |
| dc.rights.holder | The author(s) | en |
| dc.rights.uri | http://creativecommons.org/licenses/by/4.0/ | en |
| dc.title | One Fuzz Doesn't Fit All: Optimizing Directed Fuzzing via Target-tailored Program State Restriction | en |
| dc.type | Article - Refereed | en |
| dc.type.dcmitype | Text | en |