REVIEW 3 cited by
Prompt Fuzzing for Fuzz Driver Generation
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
Crafting high-quality fuzz drivers not only is time-consuming but also requires a deep understanding of the library. However, the state-of-the-art automatic fuzz driver generation techniques fall short of expectations. While fuzz drivers derived from consumer code can reach deep states, they have limited coverage. Conversely, interpretative fuzzing can explore most API calls but requires numerous attempts within a large search space. We propose PromptFuzz, a coverage-guided fuzzer for prompt fuzzing that iteratively generates fuzz drivers to explore undiscovered library code. To explore API usage in fuzz drivers during prompt fuzzing, we propose several key techniques: instructive program generation, erroneous program validation, coverage-guided prompt mutation, and constrained fuzzer scheduling. We implemented PromptFuzz and evaluated it on 14 real-world libraries. Compared with OSS-Fuzz and Hopper (the state-of-the-art fuzz driver generation tool), fuzz drivers generated by PromptFuzz achieved 1.61 and 1.63 times higher branch coverage than those by OSS-Fuzz and Hopper, respectively. Moreover, the fuzz drivers generated by PromptFuzz detected 33 genuine, new bugs out of a total of 49 crashes, out of which 30 bugs have been confirmed by their respective communities.
Forward citations
Cited by 3 Pith papers
-
An Empirical Study of Fuzz Harness Degradation
Using eight years of OSS-Fuzz data, the study shows that C/C++ fuzz harnesses keep stable coverage and bug-finding ability while they build, with about 5% of harness versions dropping by 5% coverage within six months.
-
Evaluating LLM-Based Regression Test Generation
A feedback-driven LLM tool generates regression tests for commits in minutes and, when its outputs seed a fuzzer, finds more bugs than a 24-hour state-of-the-art fuzzer on the same benchmark.
-
CKGFuzzer: LLM-Based Fuzz Driver Generation Enhanced By Code Knowledge Graph
CKGFuzzer uses a code knowledge graph to guide LLM agents in generating, repairing, and mutating fuzz drivers, reporting a pooled 8.73% relative coverage gain over PromptFuzz on eight libraries and 9 new bugs.
Discussion (0). Continue with ORCID to comment.