AFLplusplus / AFLplusplus/LibAFL

Objective Deduplication using the stack/call trace helper for QemuForkExecutor

Ouverte
#1,644 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Rust
Étoiles
2.6k
Forks
481
Merge moyen
2 j 30 min
PR mergées (30 j)
16

Description

I'm trying to implement a deduplication objective using existing crash hash, stack/call trace helper, and related objectives. The challenge is, I'm doing this for the QemuForkExecutor, and as expected, the default call trace helper in Qemu seems to have been designed for the in-process executor, and using it with a QemuForkExecutor will crash the fuzzer. I still trying to understand the inner working of LibAFL, so I was thinking about simply copying the existing helper and setting const HOOKS_DO_SIDE_EFFECTS: bool = false;. Would this be a problem? I am trying to avoid using the HitCounts map for deduplication because we could have the same crash, with the same call/stack trace but different edge hit counts, and I suppose a deduplication feedback based on the Hitcounts map woud consider such a scenario as unique crashes.
Any ideas on how to go about this would be very much appreciated.
Thanks a lot in advance.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.