一句话:提出自动化模糊测试二分定位首次触发崩溃的提交,从而缩短缺陷修复时间。
论文关注 Google 在 C/C++ 库模糊测试中发现大量安全与鲁棒性缺陷,但这些缺陷常在引入很久后才被报告,且开发者只得到触发输入和复现说明,仍需手动调试并定位引入缺陷的提交。作者介绍将 fuzzing-enabled bisection 自动化的经验:定位崩溃首次出现的 commit。基于过去一年的实践,报告开发者在该自动化分析辅助下平均修复速度快 2.23 倍,并减少关键缺陷在代码库中停留的时间。
At Google, fuzzing C/C++ libraries has discovered tens of thousands of security and robustness bugs. However, these bugs are often reported much after they were introduced. Developers are provided only with fault-inducing test inputs and replication instructions that highlight a crash, but additional debugging information may be needed to localize the cause of the bug. Hence, developers need to spend substantial time debugging the code and identifying commits that introduced the bug. In this paper, we discuss our experience with automating a fuzzing-enabled bisection that pinpoints the commit in which the crash first manifests itself. This ultimately reduces the time critical bugs stay open in our code base. We report on our experience over the past year, which shows that developers fix bugs on average 2.23 times faster when aided by this automated analysis.