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
When kAFL detects a crash, it stores the input payload generated by kAFL in the corpus/crash directory.
For structure-aware fuzzing, the harness often modifies the original payload (e.g., fixing structural fields, updating checksums, or normalizing dependent values) before forwarding it to the fuzzing target. As a result, the payload recorded by kAFL may differ from the actual input that triggers the crash.
Are there any recommended methods to record or retrieve the final payload produced by the harness at the moment kAFL detects a crash?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When kAFL detects a crash, it stores the input payload generated by kAFL in the corpus/crash directory.
For structure-aware fuzzing, the harness often modifies the original payload (e.g., fixing structural fields, updating checksums, or normalizing dependent values) before forwarding it to the fuzzing target. As a result, the payload recorded by kAFL may differ from the actual input that triggers the crash.
Are there any recommended methods to record or retrieve the final payload produced by the harness at the moment kAFL detects a crash?
Beta Was this translation helpful? Give feedback.
All reactions