Crash Report Accumulation During Continuous Fuzzing

TL;DR

This paper introduces a crash accumulation method integrated into the CASR toolset to help distinguish new errors from old ones during continuous fuzzing, addressing resource constraints and improving analysis efficiency.

Contribution

The paper presents a novel crash accumulation technique and its implementation in CASR, enhancing crash report analysis during continuous fuzzing.

Findings

Effective differentiation of new and old crashes

Improved efficiency in crash report analysis

Validated approach on fuzzing crash data

Abstract

Crash report accumulation is a necessary step during continuous fuzzing. Dynamic software analysis techniques like fuzzing and dynamic symbolic execution generate a large number of crashes for analysis. However, the time and resource constraints often lead to the postponement of fixing some less critical issues, potentially introducing new errors in future releases. Thus, there is a need to distinguish new errors from old ones. We propose a crash accumulation method and implemented it as part of the CASR toolset. We evaluated our approach on crash reports collected from fuzzing results.