You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 20, 2024. It is now read-only.
Previously, when fuzzing was performed using the "fuzz.py" script with Qiliing stable, AFL++ was able to properly identify and record when the binary crashed but now on Qiling dev, crashes do not seem to be getting caught by AFL++ anymore. It was also observed that when running "fuzz.py" without afl, two different behaviors are exhibited depending on the version of Qiling that is being used. This issue will be discussed with the authors of the Qiling project at qilingframework/qiling#1163.
Versions used
Qiling stable
Qiling Dev
Fuzzing results
Qiling stable
The crash is found instantly.
Qiling dev
No crashes found after fuzzing for 20 minutes.
Crash behavior
This is the code snippet that is used to force an artificial crash.
Discovered issue
Previously, when fuzzing was performed using the "fuzz.py" script with Qiliing stable, AFL++ was able to properly identify and record when the binary crashed but now on Qiling dev, crashes do not seem to be getting caught by AFL++ anymore. It was also observed that when running "fuzz.py" without afl, two different behaviors are exhibited depending on the version of Qiling that is being used. This issue will be discussed with the authors of the Qiling project at qilingframework/qiling#1163.
Versions used
Qiling stable
Qiling Dev
Fuzzing results
Qiling stable
The crash is found instantly.
Qiling dev
No crashes found after fuzzing for 20 minutes.
Crash behavior
This is the code snippet that is used to force an artificial crash.
Qiling stable
Qiling dev