home.social

#fuzzingtips — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fuzzingtips, aggregated by home.social.

  1. :verified: domenuk @[email protected] ·

    Just found out #LibAFL launcher can print output of child processes if you set the LIBAFL_DEBUG_OUTPUT=1 env variable.

    I knew this some time in the past, but forgot..

    #fuzzing #fuzzingTips

    #libafl #fuzzing #fuzzingtips
  2. Advanced Fuzzing League @[email protected] ·

    The deprecation of #libfuzzer is a great time to recompile your fuzzing testcases with AFL++'s afl-cc (supports the same testcases!)
    and switch your future fuzzer developments to #LibAFL

    llvm.org/docs/LibFuzzer.html#s

    #fuzzing #fuzzingTips

    #libfuzzer #libafl #fuzzing #fuzzingtips
  3. Advanced Fuzzing League @[email protected] ·

    For binary-only emulation in #LibAFL qemu, you can now dump DrCov traces to see in #idapro (lighthouse), #binaryninja (bncov), or #ghidra (dragondance) which paths the executions took.

    This helps you understand where your fuzzer gets stuck, develop the harness further, and reach greater depth in the binary, eventually.

    Binary-only modes of #AFLplusplus ( #qemu / #frida ) and libafl_frida also support DrCov output, already.

    #fuzzing #fuzzingTips
    github.com/AFLplusplus/LibAFL/

    #libafl #idapro #binaryninja #ghidra #aflplusplus #qemu