paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Reducing Time-To-Fix For Fuzzer Bugs

降低 Fuzzer 缺陷的修复时间
ASE 2021 36th IEEE/ACM International Conference on Automated Software Engineering (ASE)2021匹配度 2/10 · 论文聚焦于模糊测试缺陷的自动化二分定位以缩短修复时间,属于软件测试与调试工程,与用户关注的静态分析、LLM/Agent 程序分析、浮点程序分析及贝叶斯程序分析均无直接关联;仅在工业落地经验与自动化调试方面有较弱参考价值。引用 1 inbox
Rui Abreu, Franjo Ivancic, Filip Niksic, Hadi Ravanbakhsh, Ramesh Viswanathan
crossref: 2026-09-12

AI 速览

一句话:提出自动化模糊测试二分定位首次触发崩溃的提交,从而缩短缺陷修复时间。

论文关注 Google 在 C/C++ 库模糊测试中发现大量安全与鲁棒性缺陷,但这些缺陷常在引入很久后才被报告,且开发者只得到触发输入和复现说明,仍需手动调试并定位引入缺陷的提交。作者介绍将 fuzzing-enabled bisection 自动化的经验:定位崩溃首次出现的 commit。基于过去一年的实践,报告开发者在该自动化分析辅助下平均修复速度快 2.23 倍,并减少关键缺陷在代码库中停留的时间。

问题
在大规模 C/C++ 模糊测试中,缺陷往往在引入很久后才被报告,开发者缺乏自动定位引入提交的信息,导致调试和修复耗时较长。
方法
将模糊测试与二分查找结合并自动化,在崩溃可复现时定位该崩溃首次出现的提交,并向开发者提供该信息。
评估
基于过去一年在 Google 代码库中的实践经验,比较借助该自动化分析与否的修复时间,报告平均修复速度提升 2.23 倍,关键缺陷开放时间减少。
原文摘要(Abstract)

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.

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot6599,
  title = {Reducing Time-To-Fix For Fuzzer Bugs},
  author = {Rui Abreu and Franjo Ivancic and Filip Niksic and Hadi Ravanbakhsh and Ramesh Viswanathan},
  booktitle = {ASE},
  year = {2021},
  doi = {10.1109/ase51524.2021.9678606}
}