FairFuzz: a targeted mutation strategy for increasing greybox fuzz testing coverage
Open accessThe DOI matches its Crossref record; 29 of the 29 references it cites were found in a registry or an index.
Abstract
In recent years, fuzz testing has proven itself to be one of the most effective techniques for finding correctness bugs and security vulnerabilities in practice. One particular fuzz testing tool, American Fuzzy Lop (AFL), has become popular thanks to its ease-of-use and bug-finding power. However, AFL remains limited in the bugs it can find since it simply does not cover large regions of code. If it does not cover parts of the code, it will not find bugs there. We propose a two-pronged approach to increase the coverage achieved by AFL. First, the approach automatically identifies branches exercised by few AFL-produced inputs (rare branches), which often guard code that is empirically hard to cover by naively mutating inputs. The second part of the approach is a novel mutation mask creation algorithm, which allows mutations to be biased towards producing inputs hitting a given rare branch. This mask is dynamically computed during fuzz testing and can be adapted to other testing targets. We implement this approach on top of AFL in a tool named FairFuzz. We conduct evaluation on real-world programs against state-of-the-art versions of AFL. We find that on these programs FairFuzz achieves high branch coverage at a faster rate that state-of-the-art versions of AFL. In addition, on programs with nested conditional structure, it achieves sustained increases in branch coverage after 24 hours (average 10.6% increase). In qualitative analysis, we find that FairFuzz has an increased capacity to automatically discover keywords.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
The check wasn’t confident either way, so it gives no verdict — never disputed.
In the citing paper
“Compared to our coverage-guided baseline which only adds programs with new coverage to the seed bank for later mutation, our fitness function has minimal additional overhead.”
From Large Language Models Are Zero-Shot Fuzzers: Fuzzing Deep-Learning Libraries via Large Language Models (2023) · cites this paper as [42]
Experimental — accuracy not yet measured
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Symbolic execution and program testing
King, J. C. (1976) · Communications of the ACM · doi:10.1145/360248.360252 · Cited by 3,031 · cited 1×
“While many of the individual test inputs it generates may be garbage, due to its low computational overhead, CGF generates test inputs much faster than more sophisticated methods such as symbolic execution [17, 34] and dynamic symbolic execution (a.”
MethodCUTE: a concolic unit testing engine for C
Sen, K., Marinov, D., & Agha, G. (2005) · Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1081706.1081750 · Cited by 1,651 · cited 2×
“concolic testing) techniques [5, 7, 13, 16, 21, 22, 36, 45, 47].”
MethodSelf-citationDART: directed automated random testing
Godefroid, P., Klarlund, N., & Sen, K. (2005) · Proceedings of the 2005 ACM SIGPLAN conference on Programming language design and implementation · doi:10.1145/1065010.1065036 · Cited by 1,570 · cited 3×
“concolic testing) techniques [5, 7, 13, 16, 21, 22, 36, 45, 47].”
BackgroundMethodSelf-citationEvoSuite: automatic test suite generation for object-oriented software
Fraser, G., & Arcuri, A. (2011) · Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering · doi:10.1145/2025113.2025179 · Cited by 1,110 · cited 1×
“Evosuite [19] uses seed inputs and genetic algorithms to achieve high code coverage.”
MethodAutomated software test data generation
Korel, B. (1990) · IEEE Transactions on Software Engineering · doi:10.1109/32.57624 · Cited by 971 · cited 1×
“Search-based software testing (SBST) [19, 20, 22–24, 29, 31, 32, 42] uses optimization techniques such as hill climbing and genetic algorithms to generate inputs that optimize some observable fitness function.”
MethodDriller: Augmenting Fuzzing Through Selective Symbolic Execution
Stephens, N., Grosen, J., Salls, C., Dutcher, A., Wang, R., Corbetta, J., Shoshitaishvili, Y., Kruegel, C., & Vigna, G. (2016) · Proceedings 2016 Network and Distributed System Security Symposium · doi:10.14722/ndss.2016.23368 · Cited by 887
Finding and understanding bugs in C compilers
Yang, X., Chen, Y., Eide, E., & Regehr, J. (2011) · Proceedings of the 32nd ACM SIGPLAN Conference on Programming Language Design and Implementation · doi:10.1145/1993498.1993532 · Cited by 825 · cited 3×
“In practice, this trade-off has paid off, and fuzz testers have found numerous correctness bugs and security vulnerabilities in widely used software [9, 14, 25, 26, 28, 34, 39, 41, 43].”
BackgroundMethodBöhme, M., Pham, V.-T., Nguyen, M.-D., & Roychoudhury, A. (2017) · Proceedings of the 2017 ACM SIGSAC Conference on Computer and Communications Security · doi:10.1145/3133956.3134020 · Cited by 747 · cited 3×
“The success of one particular fuzz tester, American Fuzzy Lop (or simply AFL) [43], has gained attention both in practice and in the research community [8, 9, 30, 39].”
BackgroundMethodResultInfluentialCoverage-based Greybox Fuzzing as Markov Chain
Böhme, M., Pham, V.-T., & Roychoudhury, A. (2016) · Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security · doi:10.1145/2976749.2978428 · Cited by 649
The Current State and Future of Search Based Software Engineering
Harman, M. (2007) · Future of Software Engineering (FOSE '07) · doi:10.1109/fose.2007.29 · Cited by 631 · cited 1×
“Search-based software testing (SBST) [24, 25, 27–29, 35, 38, 39, 50] uses optimization techniques such as hill climbing and genetic algorithms to generate inputs that optimize some observable fitness function.”
Method
Research works printed but not linked: 18
- 10.5555/1763507.1763523 · doi:10.5555/1763507.1763523
- [7] Marcel Böhme. 2016. AFLFast.new. https://groups.google.com/d/msg/afl-users/ 1PmKJC-EKZ0/lbzRb8AuAAAJ. (2016). Accessed August 23rd, 2017. -
- [11] Cristian Cadar, Daniel Dunbar, and Dawson Engler. 2008. KLEE: Unassisted and Automatic Generation of High-coverage Tests for Complex Systems Programs. In Proceedings of the 8th USENIX Conference on Operating Systems Design and Implementation (OSDI'08) . -
- [13] Chris Evans, Matt Moore, and Tavis Ormandy. 2011. Fuzzing at Scale. https:// security.googleblog.com/2011/08/fuzzing-at-scale.html. (2011). Accessed August 24th, 2017. -
- [19] Mark Grechanik, Chen Fu, and Qing Xie. 2012. Automatically finding performance problems with feedback-directed learning software testing. In 2012 34th International Conference on Software Engineering (ICSE) . IEEE, 156-166. - · doi:10.5555/2337223.2337242
- [21] Istvan Haller, Asia Slowinska, Matthias Neugschwandtner, and Herbert Bos. 2013. Dowsing for Overflows: A Guided Fuzzer to Find Buffer Boundary Violations. In Proceedings of the 22Nd USENIX Conference on Security (SEC'13) . -
- [23] Mark Harman and John Clark. 2004. Metrics are fitness functions too. In Software Metrics, 2004. Proceedings. 10th International Symposium on . IEEE, 58-69. - · doi:10.5555/1018439.1021893
- [24] Mark Harman and Bryan F Jones. 2001. Search-based software engineering. Information and software Technology 43, 14 (2001), 833-839. -
- [25] Sam Hocevar. 2007. zzuf. http://caca.zoy.org/wiki/zzuf/. (2007). Accessed August 22nd, 2017. -
- [26] Christian Holler, Kim Herzig, and Andreas Zeller. 2012. Fuzzing with Code Fragments. In Presented as part of the 21st USENIX Security Symposium (USENIX Security 12) . -
- [28] Allen D. Householder and Jonathan M. Foote. 2012. Probability-Based Parameter Selection for Black-Box Fuzz Testing . Technical Report. Carnegie Mellon University Software Engineering Institute. -
- Guodong Li , Indradeep Ghosh , and Sreeranga P . Rajan . 2011 . KLOVER : A Symbolic Execution and Automatic Test Generation Tool for C++ Programs. In CAV. 609–615. Guodong Li, Indradeep Ghosh, and Sreeranga P. Rajan. 2011. KLOVER: A Symbolic Execution and Automatic Test Generation Tool for C++ Programs. In CAV. 609–615.
- 10.5555/1792786.1792798 · doi:10.5555/1792786.1792798
- [43] Michał Zalewski. 2014. American Fuzzy Lop. http://lcamtuf.coredump.cx/afl. (2014). Accessed August 18th, 2017. -
- [44] Michał Zalewski. 2016. FidgetyAFL. https://groups.google.com/d/msg/afl-users/ fOPeb62FZUg/CES5lhznDgAJ. (2016). Accessed August 23rd, 2017. -
- [45] Michał Zalewski. 2016. Unique crashes as a metric. https://groups.google.com/ d/msg/afl-users/fOPeb62FZUg/LYxgPYheDwAJ. (2016). Accessed August 24th, 2017. -
- [46] Michał Zalewski. 2017. American Fuzzy Lop Technical Details. http://lcamtuf. coredump.cx/afl/technical\_details.txt. (2017). Accessed August 18th, 2017. -
- [47] Andreas Zeller and Ralf Hildebrandt. 2002. Simplifying and Isolating FailureInducing Input. IEEE Transactions on Software Engineering 28, 2 (2002), 183-200.
Cited by
Items 101–200 of 477
Hunting for Bugs in Code Coverage Tools via Randomized Differential Testing
Yang, Y., Zhou, Y., Sun, H., Su, Z., Zuo, Z., Xu, L., & Xu, B. (2019) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2019.00061 · Cited by 30
“In practice, coverage-based fuzzing has been widely used [8], [42].”
MethodEM-Fuzz: Augmented Firmware Fuzzing via Memory Checking
Gao, J., Xu, Y., Jiang, Y., Liu, Z., Chang, W., Jiao, X., & Sun, J. (2020) · IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems · doi:10.1109/tcad.2020.3013046 · Cited by 26
“Black-box [2], [25], [26] and graybox [5], [6], [10], [12], [27]–[29] techniques play a dominant role in the field of binary”
BackgroundMethodInfluentialEvaluating and improving neural program-smoothing-based fuzzing
Wu, M., Jiang, L. L., Xiang, J., Zhang, Y., Yang, G., Ma, H., Nie, S., Wu, S., Cui, H., & Zhang, L. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510089 · Cited by 38
“Note that randomness is injected to many existing fuzzers [4, 27, 31, 50] for selecting bytes to guide mutations, e.”
BackgroundMethodInfluentialSpecDoctor: Differential Fuzz Testing to Find Transient Execution Vulnerabilities
Hur, J., Song, S., Kim, S., & Lee, B. (2022) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3548606.3560578 · Cited by 33
Zhao, K., Gong, S., & Fonseca, P. (2021) · European Conference on Computer Systems · doi:10.1145/3447786.3456258 · Cited by 27
“Other testing tools include algorithmic optimizations [44, 58]; FuZZan [37] includes more efficient metadata structures for sanitizers used in fuzzing and automatically selects the optimal structure.”
MethodNagy, S., Nguyen‐Tuong, A., Hiser, J. D., Davidson, J. W., & Hicks, M. (2021) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3460120.3484787 · Cited by 25
“AFL [59] ➤ ✔ EnFuzz [12] ➤ ✔ ProFuzzer [57] ➤ ✔ AFL++ [18] ➤ ✔ FairFuzz [34] ➤ ✔ QSYM [58] ➤ ✔ AFLFast [7] ➤ ✔ honggFuzz [49] ➤ ✗ REDQUEEN [3] ➤ ✔ AFLSmart [41] ➤ ✔ GRIMORE [5] ➤ ✔ SAVIOR [11] ➤ ✔ Angora [9] ➤ ✔ lafIntel [1] ➤ ✔ SLF [56] ➤ ✔”
BackgroundEvocatio: Conjuring Bug Capabilities from a Single PoC
Jiang, Z., Gan, S., Herrera, A., Toffalini, F., Romerio, L., Tang, C., Egele, M., Zhang, C., & Payer, M. (2022) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3548606.3560575 · Cited by 42
“Fuzzing-based taint inference has been used to overcome the previously-discussed limitations of taint analysis [2, 21, 39, 45, 76].”
MethodGuiding Greybox Fuzzing with Mutation Testing
Vikram, V., Laybourn, I., Li, A., Nair, N., OBrien, K., Sanna, R., & Padhye, R. (2023) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3597926.3598107 · Cited by 34
“The majority of fuzzing research focuses on improving heuristics such as seed-picking power schedules [9], input mutations [5, 48, 50], and coverage feedback [14, 25].”
BackgroundFuzzing Error Handling Code using Context-Sensitive Software Fault Injection
Jiang, Z. M., Bai, J. J., Lu, K., & Hu, S. M. (2020) · USENIX Security Symposium · doi:10.5555/3489212.3489358 · Cited by 24
Shah, A., She, D., Sadhu, S., Singal, K., Coffman, P., & Jana, S. (2022) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3548606.3560648 · Cited by 24
TestCov: Robust Test-Suite Execution and Coverage Measurement
Beyer, D., & Lemberger, T. (2019) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2019.00105 · Cited by 24
“TESTCOV aims at unifying and executing test suites that are created by test-case generators [7], [13], [6], [2], [9], [10], [8] for C programs.”
BackgroundMethodRapidFuzz: Accelerating fuzzing via Generative Adversarial Networks
Ye, A., Wang, L., Zhao, L., Ke, J., Wang, W., & Liu, Q. (2021) · Neurocomputing · doi:10.1016/j.neucom.2021.06.082 · Cited by 23
FIRM-COV: High-Coverage Greybox Fuzzing for IoT Firmware via Optimized Process Emulation
Kim, J., Yu, J., Kim, H., Rustamov, F., & Yun, J. (2021) · IEEE Access · doi:10.1109/access.2021.3097807 · Cited by 26
“Recent fuzzing studies have shown that traditional desktop fuzzing approaches [25], [28], [38] schedule various fuzzing factors for efficiency, whereas IoT fuzzing approaches are not conducted with scheduling.”
BackgroundA Comprehensive Survey on Software as a Service (SaaS) Transformation for the Automotive Systems
Blanco, D. F., Mouël, F. L., Lin, T., & Escudié, M.-P. (2023) · IEEE Access · doi:10.1109/access.2023.3294256 · Cited by 41
MuFuzz: Sequence-Aware Mutation and Seed Mask Guidance for Blockchain Smart Contract Fuzzing
Qian, P., Wu, H., Du, Z., Vural, T., Rong, D., Cao, Z., Zhang, L., Wang, Y., Chen, J., & He, Q. (2024) · IEEE International Conference on Data Engineering (ICDE) · doi:10.1109/icde60146.2024.00158 · Cited by 24
“After filtering out which seeds need to be mutated, MuFuzz introduces a mutation mask computation algorithm inspired by FariFuzz [56], aiming to approximate the critical parts of the test inputs that are not allowed to mutate.”
MethodLarge Language Models for Fuzzing Parsers (Registered Report)
Ackerman, J., & Cybenko, G. V. (2023) · International Fuzzing Workshop (FUZZING) · doi:10.1145/3605157.3605173 · Cited by 37
“…complexity of the targets will require that we extend the length of our fuzzing campaigns well beyond the current limit, and will necessitate the use state-of-the-art, open source, mutation fuzzers such as AFL [52], FairFuzz [31], Hongfuzz [2], or LibFuzzer [15] in our method and benchmarks.”
MethodTitan : Efficient Multi-target Directed Greybox Fuzzing
Huang, H., Yao, P., Chiu, H.-C., Guo, Y., & Zhang, C. (2024) · IEEE Symposium on Security and Privacy (S&P) · doi:10.1109/sp54263.2024.00059 · Cited by 22
“We further choose three grey-box fuzzers that optimize the seed scheduling with proper energy assigned [21], [35] and mutation strategies [16], [22] for more reliable comparison.”
BackgroundMethodInfluentialAccelerating Fuzzing through Prefix-Guided Execution
Li, S., & Su, Z. (2023) · Proceedings of the ACM on Programming Languages · doi:10.1145/3586027 · Cited by 24
“…[Lyu et al. that are likely coverage-increasing or bug-triggering, (2) tracing-cost reduction [Nagy and Hicks designs, and (3) new mutations [Lemieux and Sen 2018; She et al. 2020]: perform targeted instead foo(0, 0) 4, 6, 4, 8,12,13,14,15,17,21 ⇒ foo(0, 1) 4, 6, 4,…”
BackgroundEnhancing concurrency vulnerability detection through AST-based static fuzz mutation
Wei, Z. X., Liu, C., Deng, P., Chen, X., & Wu, X. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2025.112352 · Cited by 20
Reinforcement Learning-Based Fuzzing Technology
Zhang, Z., Cui, B., & Chen, C. (2020) · Advances in intelligent systems and computing · doi:10.1007/978-3-030-50399-4_24 · Cited by 20
Bundt, J., Fasano, A., Dolan-Gavitt, B., Robertson, W., & Leek, T. (2021) · ACM Asia Conference on Computer and Communications Security (ASIA CCS) · doi:10.1145/3433210.3453096 · Cited by 30
Sok: The Progress, Challenges, and Perspectives of Directed Greybox Fuzzing
Wang, P., Zhou, X., Yue, T., Lin, P., Liu, Y., & Lü, K. (2022) · Software Testing Verification and Reliability · doi:10.1002/stvr.1869 · Cited by 46
JIGSAW: Efficient and Scalable Path Constraints Fuzzing
Ju, C., Wang, J., Song, C., & Yin, H. (2022) · IEEE Symposium on Security and Privacy (S&P) · doi:10.1109/sp46214.2022.9833796 · Cited by 35
“This scheduling problem can be generally modeled as a multi-armed bandit (MAB) problem [16, 76] and numerous scheduling algorithms have been proposed to improve the efficiency of fuzzers [6– 8, 28, 43, 60, 70, 71, 76].”
BackgroundÖsterlund, S., Geretto, E., Jemmett, A., Güler, E., Görz, P., Holz, T., Giuffrida, C., & Bos, H. (2021) · European Workshop on System Security · doi:10.1145/3447852.3458720 · Cited by 20
Challenges and opportunities: an in-depth empirical study on configuration error injection testing
Li, W., Jia, Z., Li, S., Zhang, Y., Wang, T., Xu, E., Wang, J., & Liao, X. (2021) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3460319.3464799 · Cited by 26
“Specifically, we believe configuration error injection testing can expose more crashing bugs in new codebases, in a similar vein as other modern fuzzing techniques [15, 23, 26, 34, 36, 37, 42, 45].”
BackgroundTowards Systematic and Dynamic Task Allocation for Collaborative Parallel Fuzzing
Pham, V.-T., Nguyen, M.-D., Ta, Q.-T., Murray, T., & Rubinstein, B. I. P. (2021) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase51524.2021.9678810 · Cited by 31
“First, each fuzzing instance has a local view as well as a global view of the fuzzing information to support its optimized algorithms [7], [12].”
BackgroundFeedback-Directed Metamorphic Testing
Sun, C., Dai, H., Liu, H., & Chen, T. Y. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3533314 · Cited by 25
“For instance, FairFuzz irst executes a small number of test cases to identify branches that are di cult to cover, and then uses the branches as feedback to guide seed mutation [38].”
BackgroundHTFuzz: Heap Operation Sequence Sensitive Fuzzing
Yu, Y., Jia, X., Liu, Y., Wang, Y., Sang, Q., Zhang, C., & Su, P. (2022) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3551349.3560415 · Cited by 31
Shao, C., Li, G., Wu, J., & Zheng, X. (2024) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3640333 · Cited by 23
“Traditional code vulnerability analysis methods fell into three major categories: static analysis [1–3, 32, 39, 65], dynamic analysis [37, 48, 56], and hybrid analysis [47].”
MethodBreaking Through Binaries: Compiler-quality Instrumentation for Better Binary-only Fuzzing
Nagy, S., Nguyen‐Tuong, A., Hiser, J. D., Davidson, J. W., & Hicks, M. (2021) · USENIX Security Symposium · Cited by 19
Matryoshka: Fuzzing Deeply Nested BranchesPreprint
Chen, P., Liu, J., & Chen, H. (2019) · arXiv (Cornell University) · doi:10.48550/arxiv.1905.12228 · Cited by 19
“ese checks to cover more code. FairFuzz identifies the “rare branches” exercised by few inputs using control flow information and schedules the fuzzer to generate inputs targeting the “rare branches” [25]. If a path constraint does not exhibit taint flow dependencies on the “rare branches”, FairFuzz can solve them eff…”
BackgroundMethodInfluential1dFuzz: Reproduce 1-Day Vulnerabilities with Directed Differential Fuzzing
Yang, S., He, Y., Chen, K., Ma, Z., Luo, X., Xie, Y., Chen, J., & Zhang, C. (2023) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3597926.3598102 · Cited by 31
“Greybox fuzzing tools [1, 11, 13, 21, 27] utilize coverage to guide the fuzzer to explore more code, but in general their ability to explore specific code is limited.”
Fw‐fuzz: A code coverage‐guided fuzzing framework for network protocols on firmware
Gao, Z., Dong, W., Chang, R., & Wang, Y. (2020) · Concurrency and Computation Practice and Experience · doi:10.1002/cpe.5756 · Cited by 21
Nessie: automatically testing JavaScript APIs with asynchronous callbacks
Arteca, E., Harner, S., Pradel, M., & Tip, F. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510106 · Cited by 34
“Beyond function-level testing, application-level fuzzing has received significant attention, including AFL8 and its derivatives [9, 22], and combinations of fuzzing with symbolic testing [39].”
BackgroundAlphuzz: Monte Carlo Search on Seed-Mutation Tree for Coverage-Guided Fuzzing
Zhao, Y. C., Wang, X., Zhao, L., Cheng, Y., & Yin, H. (2022) · Annual Computer Security Applications Conference · doi:10.1145/3564625.3564660 · Cited by 19
“We fuzz each binary for 24 hours as done in previous studies [6, 24].”
BackgroundMethodResultInfluentialShapFuzz: Efficient Fuzzing via Shapley-Guided Byte Selection
Zhang, K., Zhu, X., Xiao, X., Xue, M., Zhang, C., & Wen, S. (2024) · Network and Distributed System Security Symposium · doi:10.14722/ndss.2024.23134 · Cited by 35
“We compare their performance with 10 widely-used fuzzers, including 5 byte-scheduling fuzzers (GreyOne [12], ProFuzzer [37], Angora [6], PreFuzz [36] and NEUZZ [32]) and 5 commonly used fuzzers (AFL++ [10], MOPT [25], AFLFast [3], FairFuzz [18] and AFL [40]).”
BackgroundMethodLocating vulnerabilities in binaries via memory layout recovering
Wang, H., Xie, X., Lin, S., Lin, Y., Li, Y., Qin, S., Liu, Y., & Liu, T. (2019) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3338906.3338966 · Cited by 17
Sok: The Progress, Challenges, and Perspectives of Directed Greybox FuzzingPreprint
Wang, P., Zhou, X., Lü, K., Yue, T., & Liu, Y. (2022) · SSRN Electronic Journal · doi:10.2139/ssrn.4129684 · Cited by 17
VisFuzz: Understanding and Intervening Fuzzing with Interactive Visualization
Zhou, C., Wang, M., Liang, J., Liu, Z., Sun, C. P., & Jiang, Y. (2019) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2019.00106 · Cited by 16
CrFuzz: fuzzing multi-purpose programs through input validation
Song, S., Song, C., Jang, Y., & Lee, B. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3409769 · Cited by 16
“AFLfast [10] and fair-fuzz [20] change seed scheduling algorithm to prioritize rarely-exercised branches for higher coverage.”
BackgroundAutomated Use-After-Free Detection and Exploit Mitigation: How Far Have We Gone?
Gui, B., Song, W., Xiong, H., & Huang, J. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3121994 · Cited by 24
“Compared with other standard fuzzers combined with ASan (such as AFL [112], AFLFast [113], FairFuzz [114], Angora [115], MOpt [116], and QSYM [117]), UAFL can detect more UAFs in less time.”
MethodAlbab, K. D., DiLorenzo, J., Heule, S., Kheradmand, A., Smolka, S. J., Weitz, K., Timarzi, M., Gao, J., & Yu, M. (2022) · ACM SIGCOMM Conference (SIGCOMM) · doi:10.1145/3544216.3544220 · Cited by 16
“One possibility is to use techniques that deduce mutations algorithmically [35] or via learning [23, 54].”
Saha, S., Sarker, L., Shafiuzzaman, M., Shou, C., Li, A., Sankaran, G., & Bultan, T. (2023) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3597926.3598136 · Cited by 16
“We use existing coverage-guided fuzzers AFL++ [19] and FairFuzz [25] without modification.”
BackgroundMethodResultInfluentialSJFuzz: Seed and Mutator Scheduling for JVM Fuzzing
Wu, M., Ouyang, Y., Lu, M., Chen, J., Zhao, Y., Cui, H., Yang, G., & Zhang, Y. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616277 · Cited by 24
“To bias input generation towards rare branches, Lemieux and Sen [51] proposed FairFuzz to schedule the seeds that hit rare branches for mutation.”
BackgroundYe, G., Hu, T., Tang, Z., Fan, Z., Tan, S. H., Zhang, B., Qian, W., & Wang, Z. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616332 · Cited by 28
“works [17, 38, 51, 60, 66, 69, 84] further improve code coverage for domain-specific testing by mutating the seed programs.”
BackgroundHashing Fuzzing: Introducing Input Diversity to Improve Crash Detection
Menéndez, H. D., & Clark, D. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3100858 · Cited by 16
“[18], FairFuzz[19], LibFuzzer [20] and VUzzer [51].”
BackgroundMethodInfluentialHeteroFuzz: fuzz testing to detect platform dependent divergence for heterogeneous applications
Zhang, Q., Wang, J., & Kim, M. (2021) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3468264.3468610 · Cited by 25
“create custom mutations so that the generated inputs gravitate toward exercising rare branches [33].”
BackgroundFuzzing JavaScript Engines with a Graph-based IR
Xu, H., Jiang, Z., Wang, Y., Fan, S., Xu, S., Xie, P., Fu, S., & Payer, M. (2024) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3658644.3690336 · Cited by 24
“Selecting mutation positions is a critical research topic in itself [30].”
On the Challenges of Fuzzing Techniques via Large Language Models
Huang, L., Zhao, P., Ma, L., & Chen, H. (2025) · IEEE International Conference on Software Services Engineering (SSE) · doi:10.1109/sse67621.2025.00028 · Cited by 43
“Many techniques measure code coverage, and some rely solely on code coverage as the evaluation criterion, such as FairFuzz [76].”
DeltaFuzz: Historical Version Information Guided Fuzz Testing
Zhang, J., Cui, Z., Chen, X., Wu, H., Zheng, L., & Liu, J. (2022) · Journal of Computer Science and Technology · doi:10.1007/s11390-021-1663-7 · Cited by 15
AFLNet Five Years Later: On Coverage-Guided Protocol Fuzzing
Meng, R., Pham, V.-T., Böhme, M., & Roychoudhury, A. (2025) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2025.3535925 · Cited by 18
“Once this challenge is resolved, it is worthwhile to explore other heuristics that have shown promise in (code) coverage-guided greybox fuzzing [14], [32], [4].”
Hardware Support to Improve Fuzzing Performance and Precision
Ding, R., Kim, Y., Sang, F., Xu, W. X., Saileshwar, G., & Kim, T. (2021) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3460120.3484573 · Cited by 14
“To show how SNAP can be easily adopted, we have integrated a variety of fuzzers from FuzzBench [25], including AFL [61], AFLFast [10], AFLSmart [51], FairFuzz [42], MOpt [45], and WEIZZ [16].”
MethodTensileFuzz: facilitating seed input generation in fuzzing via string constraint solving
Liu, X., You, W., Zhang, Z., & Zhang, X. (2022) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3533767.3534403 · Cited by 14
A Seed Scheduling Method With a Reinforcement Learning for a Coverage Guided Fuzzing
Choi, G., Jeon, S., Cho, J., & Moon, J. (2023) · IEEE Access · doi:10.1109/access.2022.3233875 · Cited by 16
“Greybox fuzzing uses the structural information of the target program or information obtained during execution [2], [3], [7], [9], [22], [23], [24], [25], [26].”
MethodCoverage Guided Fault Injection for Cloud Systems
Gao, Y., Dou, W., Wang, D., Feng, W., Wei, J., Zhong, H., & Huang, T. (2023) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse48619.2023.00186 · Cited by 32
Fuzzing MLIR Compiler Infrastructure via Operation Dependency Analysis
Suo, C., Chen, J., Liu, S., Jiang, J., Zhao, Y., & Wang, J. (2024) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3650212.3680360 · Cited by 23
“In the area of fuzzing, most of the existing coverage-guided fuzzing techniques take edge coverage as the guidance [6, 15, 28, 41, 44].”
AFLTurbo: Speed up Path Discovery for Greybox Fuzzing
Sun, L., Li, X., Qu, H., & Zhang, X. (2020) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre5003.2020.00017 · Cited by 14
“AFL is one of the most popular coverage-based greybox fuzzers and many researches ( [10], [11], [12], [15], [17], [21], [24], etc.) take it as baseline fuzzer.”
BackgroundMethodInfluentialCMFuzz: context-aware adaptive mutation for fuzzers
Wang, X., Hu, C., Ma, R., Tian, D., & He, J. (2021) · Empirical Software Engineering · doi:10.1007/s10664-020-09927-3 · Cited by 14
ROZZ: Property-based Fuzzing for Robotic Programs in ROS
Xie, K.-T., Bai, J.-J., Zou, Y.-H., & Wang, Y.-P. (2022) · Proceedings - IEEE International Conference on Robotics and Automation/Proceedings · doi:10.1109/icra46639.2022.9811701 · Cited by 14
“Existing fuzzing approaches focus on improving testing efficiency and effectiveness from seed selection [6], [7], [9], seed mutation [4], [5], [8], etc.”
BackgroundUltraFuzz: Towards Resource-Saving in Distributed Fuzzing
Zhou, X., Wang, P., Liu, C., Yue, T., Liu, Y., Song, C., Lü, K., Yin, Q., & Han, X. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3219520 · Cited by 25
“On average, prevalent AFL-based fuzzers, such as Fairfuzz [22], AFLFast.new [23], and FidgetyAFL [24]), only increase efficiency by around 15% when compared with original AFL.”
BackgroundMethodInfluentialSADT: syntax-aware differential testing of certificate validation in SSL/TLS implementations
Quan, L., Guo, Q., Chen, H., Xie, X., Li, X., Liu, Y., & Hu, J. (2020) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3324884.3416552 · Cited by 20
“, AFL [37], libFuzzer [28], FairFuzz [25], Steelix [26], Cerebro [27], Hawkeye [10], MUZZ [9], and UAFL [51], which mutate test cases with the guidance of customized domain-specific code coverage.”
BackgroundPhysical Devices-Agnostic Hybrid Fuzzing of IoT Firmware
Situ, L., Zhang, C., Guan, L., Zuo, Z., Wang, L., Li, X., Liu, P., & Shi, J. (2023) · IEEE Internet of Things Journal · doi:10.1109/jiot.2023.3303780 · Cited by 16
Nguyen, H. L., Nassar, N., Kehrer, T., & Grunske, L. (2020) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1145/3324884.3416668 · Cited by 13
HyperGo: Probability-based directed hybrid fuzzing
Lin, P., Wang, P., Zhou, X., Xie, W., Lü, K., & Zhang, G. (2024) · Computers & Security · doi:10.1016/j.cose.2024.103851 · Cited by 12
DDGF: Dynamic Directed Greybox Fuzzing with Path Profiling
Fang, H., Zhang, K. F., Yu, D., & Zhang, Y. (2024) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3650212.3680324 · Cited by 18
“Coverage feedback[27, 34, 39, 46, 46] is the most critical part of grey-box fuzzing.”
BackgroundConfuzzion: A Java Virtual Machine Fuzzer for Type Confusion Vulnerabilities
Bonnaventure, W., Khanfir, A., Bartel, A., Papadakis, M., & Traon, Y. L. (2021) · IEEE International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs54544.2021.00069 · Cited by 17
Opening Pandora's box through ATFuzzer
Karim, I., Cicala, F., Hussain, S. R., Chowdhury, O., & Bertino, E. (2019) · Annual Computer Security Applications Conference · doi:10.1145/3359789.3359833 · Cited by 12
“…has been carried out to develop sophisticated techniques to improve mutation strategies— coverage information through instrumenting the binary [28, 36, 37, 59]; resource usage information [35, 46]; control and data flow features [48]; static vulnerability prediction models [38]; data-driven seed…”
MethodGreybox fuzzing as a contextual bandits problemPreprint
Patil, K., & Kanade, A. (2018) · arXiv (Cornell University) · doi:10.48550/arxiv.1806.03806 · Cited by 12
PTrix: Efficient Hardware-Assisted Fuzzing for COTS BinaryPreprint
Chen, Y., Mu, D., Xu, J., Sun, Z., Shen, W., Xing, X., Lu, L. J., & Mao, B. (2019) · arXiv (Cornell University) · doi:10.48550/arxiv.1905.10499 · Cited by 12
“Code exploration efficiency: We calculated the code coverage using a representative quantification — number of edges between basic blocks [23] and summarize the results in Figure 8.”
BackgroundMethodZigZagFuzz: Interleaved Fuzzing of Program Options and Files
Lee, A., Choi, Y., Hong, S., Kim, Y., Cho, K., & Kim, M. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3697014 · Cited by 15
“FairFuzz [21] and Vuzzer [33] favor inputs which execute rarely executed branches and which execute basic blocks located in deep control-structure, respectively.”
Profile-guided System Optimizations for Accelerated Greybox Fuzzing
Zhang, Y., Pang, C., Nagy, S., Chen, X., & Xu, J. L. (2023) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3576915.3616636 · Cited by 16
“For better generality, we consider AFL [86] (version 2.57b) since its system-level designs have been followed by many other tools [41, 42, 45, 49, 56, 63, 67, 85] Experimental Setup: To support the study, we gather a set of 12 projects included in the OSS-Fuzz program [79] (summarized in Table 1).”
MethodHuang, H., Zhou, A., Payer, M., & Zhang, C. (2024) · IEEE Symposium on Security and Privacy (S&P) · doi:10.1109/sp54263.2024.00142 · Cited by 27
“Other than random mutation, Fairfuzz [50] identifies the input offsets where the values are not necessary to change, Thus, minimizing the input search space improves the efficiency of mutation.”
BackgroundFacilitating Parallel Fuzzing with Mutually-Exclusive Task Distribution
Wang, Y., Zhang, Y., Pang, C., Li, P., Triandopoulos, N., & Xu, J. (2021) · Lecture notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering · doi:10.1007/978-3-030-90022-9_10 · Cited by 17
Program State Sensitive Parallel Fuzzing for Real World Software
Ye, J., Zhang, B., Li, R., Feng, C., & Tang, C. (2019) · IEEE Access · doi:10.1109/access.2019.2905744 · Cited by 11
“Our method first identifies the key offsets in the test case that are related to the path constraints [18].”
BackgroundMethodTurtiainen, H., Costin, A., Khandker, S., & Hämäläinen, T. (2022) · IEEE Access · doi:10.1109/access.2022.3150840 · Cited by 12
ovAFLow: Detecting Memory Corruption Bugs with Fuzzing-Based Taint Inference
Zhang, G., Wang, P., Yue, T., Kong, X., Zhou, X., & Lü, K. (2022) · Journal of Computer Science and Technology · doi:10.1007/s11390-021-1600-9 · Cited by 10
AflIot: Fuzzing on linux-based IoT device with binary-level instrumentation
Du, X., Chen, A., He, B., Chen, H., Zhang, F., & Chen, Y. (2022) · Computers & Security · doi:10.1016/j.cose.2022.102889 · Cited by 10
“Most of those improvements, such as ( Böhme et al., 2017a; 2017b; Gan et al., 2018; Lemieux and Sen, 2018 ), are based on AFL fuzzer.”
BackgroundMethodResultInfluentialImproving fuzzing assessment methods through the analysis of metrics and experimental conditions
Eceiza, M., Flores, J. L., & Iturbe, M. (2022) · Computers & Security · doi:10.1016/j.cose.2022.102946 · Cited by 11
Cooperative verifier-based testing with CoVeriTest
Beyer, D., & Jakobs, M.-C. (2021) · International Journal on Software Tools for Technology Transfer · doi:10.1007/s10009-020-00587-8 · Cited by 16
“Existing, automatic testgeneration techniques in this area range from random testing [68,104] and fuzzing [50,95,96], over search-based testing”
MethodKCFuzz: Directed Fuzzing Based on Keypoint Coverage
Wang, S., Jiang, X., Yu, X., & Sun, S. (2021) · Lecture notes in computer science · doi:10.1007/978-3-030-78609-0_27 · Cited by 10
TOFU: Target-Orienter FUzzer.Preprint
Wang, Z., Liblit, B., & Reps, T. (2020) · arXiv (Cornell University) · Cited by 10
Balance Seed Scheduling via Monte Carlo Planning
Huang, H., Chiu, H.-C., Shi, Q., Yao, P., & Zhang, C. (2023) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2023.3285293 · Cited by 9
“Wehaveimplemented our method as a greybox fuzzer named B ELIEF F UZZ on top of AFL [1] and compared it to seven state-of-the-art coverage-based greybox fuzzers, AFL, AFL++ [15], FairFuzz [24], AFLFast [7], EcoFuzz [40], K-Scheduler [34], and Alphuzz [42].”
BackgroundMethodInfluentialGreen Fuzzing: A Saturation-Based Stopping Criterion using Vulnerability Prediction
Lipp, S., Elsner, D., Kacianka, S., Pretschner, A., Böhme, M., & Bănescu, S. (2023) · ACM SIGSOFT International Symposium on Software Testing and Analysis (ISSTA) · doi:10.1145/3597926.3598043 · Cited by 18
“Our dataset contains the crash and coverage data of eight state-of-the-art greybox fuzzers: AFL [2],AFLFast [18],AFL++ [25],AFLSmart [61], FairFuzz [40], Honggfuzz [8],MOpt-AFL [47], andMOpt-AFL++ [25].”
MethodInfluentialAn In-depth Analysis of Duplicated Linux Kernel Bug Reports
Mu, D., Wu, Y., Chen, Y., Lin, Z., Yu, C., Xing, X., & Wang, G. (2022) · Network and Distributed System Security Symposium · doi:10.14722/ndss.2022.24159 · Cited by 9
“…method considers the basic block transition in the execution path, which is widely employed by AFL-based fuzzers ( e.g., [23], [22], [67], [21], [57], [62], [53], [56]) Unfortunately, a study by Klees et al. [52] shows that this approach could yield excessive false positives and false negatives.”
MethodFuzzTastic: a fine-grained, fuzzer-agnostic coverage analyzer
Lipp, S., Elsner, D., Hutzelmann, T., Bănescu, S., Pretschner, A., & Böhme, M. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510454.3516847 · Cited by 15
“Furthermore, we include FairFuzz [12] (2.”
Daisy: Effective Fuzz Driver Synthesis with Object Usage Sequence Analysis
Zhang, M., Zhou, C., Liu, J., Wang, M., Liang, J., Zhu, J., & Jiang, Y. (2023) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip58684.2023.00013 · Cited by 13
“As the number of program states can be infinite, researchers and developers have devised a number of techniques [14], [15], [16], [17], [18], [19], [20] that allow fuzzers to cover more code and trigger more bugs.”
BackgroundLEAP: Efficient and Automated Test Method for NLP Software
Xiao, M., Xiao, Y., Dong, H., Ji, S., & Zhang, P. (2023) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase56229.2023.00052 · Cited by 15
Instiller: Toward Efficient and Realistic RTL Fuzzing
Zhang, G., Wang, P., Yue, T., Liu, D., Guo, Y., & Lü, K. (2024) · IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems · doi:10.1109/tcad.2024.3360318 · Cited by 8
MicroFuzz: An Efficient Fuzzing Framework for Microservices
Di, P., Liu, B., & Gao, Y. (2024) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1145/3639477.3639723 · Cited by 8
Fuzzing JavaScript engines with a syntax-aware neural program model
Xu, H., Wang, Y., Jiang, Z., Fan, S., Fu, S., & Xie, P. (2024) · Computers & Security · doi:10.1016/j.cose.2024.103947 · Cited by 13
My Fuzzers Won’t Build: An Empirical Study of Fuzzing Build Failures
Nourry, O., Kashiwa, Y., Shang, W., Shu, H., & Kamei, Y. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3688842 · Cited by 22
“While the field of fuzzing has many publications on fuzzing tools and techniques to improve fuzzing coverage [31, 57, 58], the lack of open source empirical data has limited the ability of researchers to investigate fuzzing practices and methodologies so far.”
FOX: Coverage-guided Fuzzing as Online Stochastic Control
She, D., Storek, A., Xie, Y., Kweon, S., Srivastava, P., & Jana, S. (2024) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3658644.3670362 · Cited by 8
InstruGuard: Find and Fix Instrumentation Errors for Coverage-based Greybox Fuzzing
Liu, Y., Wang, Y., Su, P., Yu, Y., & Jia, X. (2021) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase51524.2021.9678671 · Cited by 8
“…built a dataset of 15 real-world programs collected from recent fuzzing papers as our targets [10, 12, 13, 18, 27, 29, 36, 46, 50] and selected 6 representative greybox and whitebox fuzzers (i.e., AFL [52], FairFuzz [24], MOPT [27], Memlock [47], AFL++ [16], and Angora [10]) to study the impacts.”
BackgroundMethodImproving the performance of code vulnerability prediction using abstract syntax tree information
Debeyan, F. A., Hall, T., & Bowes, D. (2022) · doi:10.1145/3558489.3559066 · Cited by 8
“Code analysis can either be static where static properties of the code, such as AST [25], Flow/Dependency graphs [19, 47], are analyzed, or dynamic where analysers execute the program and detect potential vulnerabilities of the program in the runtime behavior of the program [47].”
BackgroundSurgeFuzz: Surge-Aware Directed Fuzzing for CPU Designs
Sugiyama, Y., Matsuo, R., & Shioya, R. (2023) · doi:10.1109/iccad57390.2023.10323819 · Cited by 15
“In the field of software fuzzing, there exist methods that target hard-to-test corner cases and rare states, similar to our approach [39], [45]–[47].”
BackgroundMethodFuSeBMC v4: Improving Code Coverage with Smart Seeds via BMC, Fuzzing and Static Analysis
Alshmrany, K. M., Aldughaim, M., Bhayat, A., & Cordeiro, L. C. (2024) · Formal Aspects of Computing · doi:10.1145/3665337 · Cited by 11
“FairFuzz [54] is a grey-box fuzzer that utilizes guided-mutation.”
BackgroundEngineering a Better Fuzzer with Synergically Integrated Optimizations
Liang, J., Chen, Y., Wang, M., Jiang, Y., Yang, Z., Sun, C. P., Jiao, X., & Sun, J. (2019) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre.2019.00018 · Cited by 8
Path Sensitive Fuzzing for Native Applications
Gan, S., Zhang, C., Qin, X., Tu, X., Li, K., Pei, Z., & Chen, Z. (2020) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2020.3027690 · Cited by 8
Vulnerable Region-Aware Greybox Fuzzing
Situ, L., Zuo, Z., Guan, L., Wang, L.-Z., Li, X., Shi, J., & Liu, P. (2021) · Journal of Computer Science and Technology · doi:10.1007/s11390-021-1196-0 · Cited by 9
“On top of AFL, a lot of variants such as AFLFast [13] , AFLSmart [14] FairFuzz [20] , AFLGo [21] , CollAFL [22] and Angora [23] have been proposed.”
BackgroundInfluentialVall-nut: Principled Anti-Grey box - Fuzzing
Li, Y., Meng, G., Xu, J., Zhang, C., Chen, H., Xie, X., Wang, H., & Liu, Y. (2021) · Proceedings/Proceedings - International Symposium on Software Reliability Engineering · doi:10.1109/issre52982.2021.00039 · Cited by 8
Metadata
- Authors
- Lemieux, C., & Sen, K.
- Affiliations
- University of California, Berkeley (US)
- Venue
- Proceedings of the 33rd ACM/IEEE International Conference on Automated Software Engineering
- Publisher
- ACM
- Published
- 2018-09-03
- Pages
- 475-485
- OpenAlex
- W2757104921
- Cited by
- 477
- References
- 29
- Citations by year
- 2026: 39 · 2025: 60 · 2024: 69 · 2023: 65 · 2022: 62 · 2021: 68 · 2020: 59 · 2019: 47 · 2018: 8
- FWCI
- 30.83
- Type
- conference paper
- Language
- en
- Open access
- green
- arxiv.org
- Locations
- IEEE/ACM International Conference on Automated Software Engineering (ASE) (publishedVersion)
- arXiv (Cornell University) (submittedVersion)
- Funders
- National Science Foundation (CCF-1409872, CCF-1423645)
- Topics
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Physical Sciences › Computer Science › Hardware and Architecture › Security and Verification in Computing
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Keywords
- targeted mutations, branch coverage, code coverage, software testing, bug detection
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.