diff options
| -rw-r--r-- | utils/autodict_ql/build-codeql.sh | 2 | ||||
| -rw-r--r-- | utils/autodict_ql/litool.ql | 2 | ||||
| -rw-r--r-- | utils/autodict_ql/readme.md | 3 |
3 files changed, 3 insertions, 4 deletions
diff --git a/utils/autodict_ql/build-codeql.sh b/utils/autodict_ql/build-codeql.sh index 450207f6..6ae4b362 100644 --- a/utils/autodict_ql/build-codeql.sh +++ b/utils/autodict_ql/build-codeql.sh @@ -14,4 +14,4 @@ export "PATH=~/codeql-home/codeql-cli/:$PATH" echo "export PATH=~/codeql-home/codeql-cli/:$PATH" >> ~/.bashrc codeql resolve languages codeql resolve qlpacks -codeql \ No newline at end of file +codeql diff --git a/utils/autodict_ql/litool.ql b/utils/autodict_ql/litool.ql index b7f4bf33..76f429c1 100644 --- a/utils/autodict_ql/litool.ql +++ b/utils/autodict_ql/litool.ql @@ -7,4 +7,4 @@ class HexOrOctLiteral extends Literal{ } from HexOrOctLiteral lit -select lit.getValueText() \ No newline at end of file +select lit.getValueText() diff --git a/utils/autodict_ql/readme.md b/utils/autodict_ql/readme.md index 31a20352..9170f552 100644 --- a/utils/autodict_ql/readme.md +++ b/utils/autodict_ql/readme.md @@ -89,7 +89,7 @@ Commands: ## More on dictionaries and tokens Core developer of the AFL++ project Marc Heuse also developed a similar tool named `dict2file` which is a LLVM pass which can automatically extract useful tokens, in addition with LTO instrumentation mode, this dict2file is automatically generates token extraction. `Autodict-QL` plugin gives you scripting capability and you can do whatever you want to extract from the Codebase and it's up to you. In addition it's independent from LLVM system. -On the other hand, you can also use Google dictionaries which have been made public in May 2020, but the problem of using Google dictionaries is that they are limited to specific file format and speicifications. For example, for testing binutils and ELF file format or AVI in FFMPEG, there are no prebuilt dictionaries, so it is highly recommended to use `Autodict-QL` or `Dict2File` features to automatically generate dictionaries based on the target. +On the other hand, you can also use Google dictionaries which have been made public in May 2020, but the problem of using Google dictionaries is that they are limited to specific file formats and specifications. For example, for testing binutils and ELF file format or AVI in FFMPEG, there are no prebuilt dictionaries, so it is highly recommended to use `Autodict-QL` or `Dict2File` features to automatically generate dictionaries based on the target. I've personally prefered to use `Autodict-QL` or `dict2file` rather than Google dictionaries or any other manually generated dictionaries as `Autodict-QL` and `dict2file` are working based on the target. In overall, fuzzing with dictionaries and well-generated tokens will give better results. @@ -98,4 +98,3 @@ There are 2 important points to remember : - If you combine `Autodict-QL` with AFL++ cmplog, you will get much better code coverage and hence better chances to discover new bugs. - Do not forget to set `AFL_MAX_DET_EXTRAS` at least to the number of generated dictionaries. If you forget to set this environment variable, then AFL++ uses just 200 tokens and use the rest of them only probabilistically. So this will guarantee that your tokens will be used by AFL++. - |