You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
51 lines
1.7 KiB
51 lines
1.7 KiB
1 month ago
|
# TODO list for AFL++
|
||
|
|
|
||
|
|
## Must
|
||
|
|
|
||
|
|
- ijon support?
|
||
|
|
- check for null ptr for xml/curl/g_ string transform functions
|
||
|
|
- hardened_usercopy=0 page_alloc.shuffle=0
|
||
|
|
- add value_profile but only enable after 15 minutes without finds
|
||
|
|
- cmplog max items env?
|
||
|
|
- adapt MOpt to new mutation engine
|
||
|
|
- Update afl->pending_not_fuzzed for MOpt
|
||
|
|
- cmplog rtn sanity check on fixed length? currently we ignore the length
|
||
|
|
- afl-showmap -f support
|
||
|
|
- afl-fuzz multicore wrapper script
|
||
|
|
- when trimming then perform crash detection
|
||
|
|
|
||
|
|
|
||
|
|
## Should
|
||
|
|
|
||
|
|
- afl-crash-analysis
|
||
|
|
- cmplog: add loop count resolving (byte -> loop cnt change, calc special values)
|
||
|
|
- support persistent and deferred fork server in afl-showmap?
|
||
|
|
- better autodetection of shifting runtime timeout values
|
||
|
|
- afl-plot to support multiple plot_data
|
||
|
|
- parallel builds for source-only targets
|
||
|
|
- get rid of check_binary, replace with more forkserver communication
|
||
|
|
- first fuzzer should be a main automatically? not sure.
|
||
|
|
|
||
|
|
## Maybe
|
||
|
|
|
||
|
|
- forkserver tells afl-fuzz if cmplog is supported and if so enable
|
||
|
|
it by default, with AFL_CMPLOG_NO=1 (?) set to skip?
|
||
|
|
- afl_custom_splice()
|
||
|
|
- cmdline option from-to range for mutations
|
||
|
|
|
||
|
|
## Further down the road
|
||
|
|
|
||
|
|
QEMU mode/FRIDA mode:
|
||
|
|
- non colliding instrumentation
|
||
|
|
- rename qemu specific envs to AFL_QEMU (AFL_ENTRYPOINT, AFL_CODE_START/END,
|
||
|
|
AFL_COMPCOV_LEVEL?)
|
||
|
|
- add AFL_QEMU_EXITPOINT (maybe multiple?)
|
||
|
|
|
||
|
|
## Ideas
|
||
|
|
|
||
|
|
- LTO/sancov: write current edge to prev_loc and use that information when
|
||
|
|
using cmplog or __sanitizer_cov_trace_cmp*. maybe we can deduct by follow up
|
||
|
|
edge numbers that both following cmp paths have been found and then disable
|
||
|
|
working on this edge id -> cmplog_intelligence branch
|
||
|
|
- use cmplog colorization taint result for havoc locations?
|