ExternalVendorCode/AFLplusplus
1
0
Fork 0
mirror of https://github.com/AFLplusplus/AFLplusplus.git synced 2025-06-08 08:11:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

incorporated most of the 2.53b changes

Browse Source
This commit is contained in:
van Hauser 2019-07-26 10:35:58 +02:00
parent db2392b778
commit 8f4f45c524
5 changed files with 106 additions and 92 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README
View File

@ -1 +0,0 @@
docs/README

187
docs/README → README.md
View File

@ -1,55 +1,48 @@
============================ # american fuzzy lop plus plus (afl++)
american fuzzy lop plus plus
============================
Originally written by Michal Zalewski <lcamtuf@google.com> Originally developed by Michal "lcamtuf" Zalewski.
Repository: https://github.com/vanhauser-thc/AFLplusplus Repository: [https://github.com/vanhauser-thc/AFLplusplus](https://github.com/vanhauser-thc/AFLplusplus)
afl++ is maintained by Marc Heuse <mh@mh-sec.de>, Heiko Eissfeldt afl++ is maintained by Marc Heuse <mh@mh-sec.de>, Heiko Eissfeldt
<heiko.eissfeldt@hexco.de> and Andrea Fioraldi <andreafioraldi@gmail.com> as <heiko.eissfeldt@hexco.de> and Andrea Fioraldi <andreafioraldi@gmail.com>.
there have been no updates to afl since November 2017.
## The enhancements compared to the original stock afl
Many improvements were made, e.g. more performant llvm_mode, supporting Many improvements were made over the official afl release - which did not
get any improvements since November 2017.
Among others afl++ has, e.g. more performant llvm_mode, supporting
llvm up to version 8, Qemu 3.1, more speed and crashfixes for Qemu, llvm up to version 8, Qemu 3.1, more speed and crashfixes for Qemu,
laf-intel feature for Qemu (with libcompcov) etc. laf-intel feature for Qemu (with libcompcov) and more.
Additionally AFLfast's power schedules by Marcel Boehme from Additionally the following patches have been integrated:
https://github.com/mboehme/aflfast have been incorporated.
C. Hollers afl-fuzz Python mutator module and llvm_mode whitelist support * AFLfast's power schedules by Marcel Boehme: [https://github.com/mboehme/aflfast](https://github.com/mboehme/aflfast)
was added too (https://github.com/choller/afl)
New is the excellent MOpt mutator from * C. Hollers afl-fuzz Python mutator module and llvm_mode whitelist support: [https://github.com/choller/afl](https://github.com/choller/afl)
https://github.com/puppet-meteor/MOpt-AFL
Also newly integrated is instrim, a very effective CFG llvm_mode * the new excellent MOpt mutator: [https://github.com/puppet-meteor/MOpt-AFL](https://github.com/puppet-meteor/MOpt-AFL)
instrumentation implementation from https://github.com/csienslab/instrim
And finally the newest addition is the unicorn_mode which allows fuzzing * instrim, a very effective CFG llvm_mode instrumentation implementation for large targets: [https://github.com/csienslab/instrim](https://github.com/csienslab/instrim)
of binaries from completely different platforms - provided by domenukk!
The unicorn afl mode is not the stock version but like afl++ contains * unicorn_mode which allows fuzzing of binaries from completely different platforms (integration provided by domenukk)
various patches from forks that make it better :)
A more thorough list is available in the PATCHES file. A more thorough list is available in the PATCHES file.
So all in all this is the best-of AFL that is currently out there :-) So all in all this is the best-of AFL that is currently out there :-)
Copyright 2013, 2014, 2015, 2016 Google Inc. All rights reserved.
Released under terms and conditions of Apache License, Version 2.0.
For new versions and additional information, check out: For new versions and additional information, check out:
https://github.com/vanhauser-thc/AFLplusplus [https://github.com/vanhauser-thc/AFLplusplus](https://github.com/vanhauser-thc/AFLplusplus)
To compare notes with other users or get notified about major new features, To compare notes with other users or get notified about major new features,
send a mail to <afl-users+subscribe@googlegroups.com>. send a mail to <afl-users+subscribe@googlegroups.com>.
** See QuickStartGuide.txt if you don't have time to read this file. ** See [docs/QuickStartGuide.txt](docs/QuickStartGuide.txt) if you don't have time to
read this file.
1) Challenges of guided fuzzing ## 1) Challenges of guided fuzzing
------------------------------- -------------------------------
Fuzzing is one of the most powerful and proven strategies for identifying Fuzzing is one of the most powerful and proven strategies for identifying
@ -77,8 +70,7 @@ to suffer from reliability and performance problems in practical uses - and
currently do not offer a viable alternative to "dumb" fuzzing techniques. currently do not offer a viable alternative to "dumb" fuzzing techniques.
2) The afl-fuzz approach ## 2) The afl-fuzz approach
------------------------
American Fuzzy Lop is a brute-force fuzzer coupled with an exceedingly simple American Fuzzy Lop is a brute-force fuzzer coupled with an exceedingly simple
but rock-solid instrumentation-guided genetic algorithm. It uses a modified but rock-solid instrumentation-guided genetic algorithm. It uses a modified
@ -117,8 +109,7 @@ The fuzzer is thoroughly tested to deliver out-of-the-box performance far
superior to blind fuzzing or coverage-only tools. superior to blind fuzzing or coverage-only tools.
3) Instrumenting programs for use with AFL ## 3) Instrumenting programs for use with AFL
------------------------------------------
PLEASE NOTE: llvm_mode compilation with afl-clang-fast/afl-clang-fast++ PLEASE NOTE: llvm_mode compilation with afl-clang-fast/afl-clang-fast++
instead of afl-gcc/afl-g++ is much faster and has a few cool features. instead of afl-gcc/afl-g++ is much faster and has a few cool features.
@ -136,39 +127,45 @@ or even faster than possible with traditional tools.
The correct way to recompile the target program may vary depending on the The correct way to recompile the target program may vary depending on the
specifics of the build process, but a nearly-universal approach would be: specifics of the build process, but a nearly-universal approach would be:
```shell
$ CC=/path/to/afl/afl-gcc ./configure $ CC=/path/to/afl/afl-gcc ./configure
$ make clean all $ make clean all
```
For C++ programs, you'd would also want to set CXX=/path/to/afl/afl-g++. For C++ programs, you'd would also want to set `CXX=/path/to/afl/afl-g++`.
The clang wrappers (afl-clang and afl-clang++) can be used in the same way; The clang wrappers (afl-clang and afl-clang++) can be used in the same way;
clang users may also opt to leverage a higher-performance instrumentation mode, clang users may also opt to leverage a higher-performance instrumentation mode,
as described in llvm_mode/README.llvm. as described in [llvm_mode/README.llvm](llvm_mode/README.llvm).
Clang/LLVM has a much better performance and works from LLVM version 4.0 to 8. Clang/LLVM has a much better performance and works with LLVM version 4.0 to 8.
Using the LAF Intel performance enhancements are also recommended, see Using the LAF Intel performance enhancements are also recommended, see
llvm_mode/README.laf-intel [llvm_mode/README.laf-intel](llvm_mode/README.laf-intel)
Using partial instrumentation is also recommended, see Using partial instrumentation is also recommended, see
llvm_mode/README.whitelist [llvm_mode/README.whitelist](llvm_mode/README.whitelist)
When testing libraries, you need to find or write a simple program that reads When testing libraries, you need to find or write a simple program that reads
data from stdin or from a file and passes it to the tested library. In such a data from stdin or from a file and passes it to the tested library. In such a
case, it is essential to link this executable against a static version of the case, it is essential to link this executable against a static version of the
instrumented library, or to make sure that the correct .so file is loaded at instrumented library, or to make sure that the correct .so file is loaded at
runtime (usually by setting LD_LIBRARY_PATH). The simplest option is a static runtime (usually by setting `LD_LIBRARY_PATH`). The simplest option is a static
build, usually possible via: build, usually possible via:
```shell
$ CC=/path/to/afl/afl-gcc ./configure --disable-shared $ CC=/path/to/afl/afl-gcc ./configure --disable-shared
```
Setting AFL_HARDEN=1 when calling 'make' will cause the CC wrapper to Setting `AFL_HARDEN=1` when calling 'make' will cause the CC wrapper to
automatically enable code hardening options that make it easier to detect automatically enable code hardening options that make it easier to detect
simple memory bugs. Libdislocator, a helper library included with AFL (see simple memory bugs. Libdislocator, a helper library included with AFL (see
libdislocator/README.dislocator) can help uncover heap corruption issues, too. [libdislocator/README.dislocator](libdislocator/README.dislocator)) can help uncover heap corruption issues, too.
PS. ASAN users are advised to docs/review notes_for_asan.txt file for PS. ASAN users are advised to review [docs/notes_for_asan.txt](docs/notes_for_asan.txt)
important caveats. file for important caveats.
4) Instrumenting binary-only apps ## 4) Instrumenting binary-only apps
--------------------------------- ---------------------------------
When source code is *NOT* available, the fuzzer offers experimental support for When source code is *NOT* available, the fuzzer offers experimental support for
@ -178,10 +175,12 @@ with a version of QEMU running in the lesser-known "user space emulation" mode.
QEMU is a project separate from AFL, but you can conveniently build the QEMU is a project separate from AFL, but you can conveniently build the
feature by doing: feature by doing:
```shell
$ cd qemu_mode $ cd qemu_mode
$ ./build_qemu_support.sh $ ./build_qemu_support.sh
```
For additional instructions and caveats, see qemu_mode/README.qemu. For additional instructions and caveats, see [qemu_mode/README.qemu](qemu_mode/README.qemu).
The mode is approximately 2-5x slower than compile-time instrumentation, is The mode is approximately 2-5x slower than compile-time instrumentation, is
less conductive to parallelization, and may have some other quirks. less conductive to parallelization, and may have some other quirks.
@ -190,8 +189,11 @@ If [afl-dyninst](https://github.com/vanhauser-thc/afl-dyninst) works for
your binary, then you can use afl-fuzz normally and it will have twice your binary, then you can use afl-fuzz normally and it will have twice
the speed compared to qemu_mode. the speed compared to qemu_mode.
A more comprehensive description of these and other options can be found in
[docs/binaryonly_fuzzing.txt](docs/binaryonly_fuzzing.txt)
5) Power schedules
## 5) Power schedules
------------------ ------------------
The power schedules were copied from Marcel Böhme's excellent AFLfast The power schedules were copied from Marcel Böhme's excellent AFLfast
@ -220,9 +222,10 @@ made the default mode).
More details can be found in the paper published at the 23rd ACM Conference on More details can be found in the paper published at the 23rd ACM Conference on
Computer and Communications Security (CCS'16): Computer and Communications Security (CCS'16):
https://www.sigsac.org/ccs/CCS2016/accepted-papers/ (https://www.sigsac.org/ccs/CCS2016/accepted-papers/)[https://www.sigsac.org/ccs/CCS2016/accepted-papers/]
6) Choosing initial test cases
## 6) Choosing initial test cases
------------------------------ ------------------------------
To operate correctly, the fuzzer requires one or more starting file that To operate correctly, the fuzzer requires one or more starting file that
@ -230,7 +233,7 @@ contains a good example of the input data normally expected by the targeted
application. There are two basic rules: application. There are two basic rules:
- Keep the files small. Under 1 kB is ideal, although not strictly necessary. - Keep the files small. Under 1 kB is ideal, although not strictly necessary.
For a discussion of why size matters, see perf_tips.txt. For a discussion of why size matters, see [perf_tips.txt](docs/perf_tips.txt).
- Use multiple test cases only if they are functionally different from - Use multiple test cases only if they are functionally different from
each other. There is no point in using fifty different vacation photos each other. There is no point in using fifty different vacation photos
@ -244,7 +247,7 @@ the afl-cmin utility to identify a subset of functionally distinct files that
exercise different code paths in the target binary. exercise different code paths in the target binary.
7) Fuzzing binaries ## 7) Fuzzing binaries
------------------- -------------------
The fuzzing process itself is carried out by the afl-fuzz utility. This program The fuzzing process itself is carried out by the afl-fuzz utility. This program
@ -253,13 +256,17 @@ store its findings, plus a path to the binary to test.
For target binaries that accept input directly from stdin, the usual syntax is: For target binaries that accept input directly from stdin, the usual syntax is:
```shell
$ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program [...params...] $ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program [...params...]
```
For programs that take input from a file, use '@@' to mark the location in For programs that take input from a file, use '@@' to mark the location in
the target's command line where the input file name should be placed. The the target's command line where the input file name should be placed. The
fuzzer will substitute this for you: fuzzer will substitute this for you:
```shell
$ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program @@ $ ./afl-fuzz -i testcase_dir -o findings_dir /path/to/program @@
```
You can also use the -f option to have the mutated data written to a specific You can also use the -f option to have the mutated data written to a specific
file. This is useful if the program expects a particular file extension or so. file. This is useful if the program expects a particular file extension or so.
@ -271,7 +278,7 @@ You can use -t and -m to override the default timeout and memory limit for the
executed process; rare examples of targets that may need these settings touched executed process; rare examples of targets that may need these settings touched
include compilers and video decoders. include compilers and video decoders.
Tips for optimizing fuzzing performance are discussed in perf_tips.txt. Tips for optimizing fuzzing performance are discussed in [perf_tips.txt](docs/perf_tips.txt).
Note that afl-fuzz starts by performing an array of deterministic fuzzing Note that afl-fuzz starts by performing an array of deterministic fuzzing
steps, which can take several days, but tend to produce neat test cases. If you steps, which can take several days, but tend to produce neat test cases. If you
@ -279,12 +286,12 @@ want quick & dirty results right away - akin to zzuf and other traditional
fuzzers - add the -d option to the command line. fuzzers - add the -d option to the command line.
8) Interpreting output ## 8) Interpreting output
---------------------- ----------------------
See the status_screen.txt file for information on how to interpret the See the [docs/status_screen.txt](docs/status_screen.txt) file for information on
displayed stats and monitor the health of the process. Be sure to consult this how to interpret the displayed stats and monitor the health of the process. Be
file especially if any UI elements are highlighted in red. sure to consult this file especially if any UI elements are highlighted in red.
The fuzzing process will continue until you press Ctrl-C. At minimum, you want The fuzzing process will continue until you press Ctrl-C. At minimum, you want
to allow the fuzzer to complete one queue cycle, which may take anywhere from a to allow the fuzzer to complete one queue cycle, which may take anywhere from a
@ -322,35 +329,39 @@ queue entries. This should help with debugging.
When you can't reproduce a crash found by afl-fuzz, the most likely cause is When you can't reproduce a crash found by afl-fuzz, the most likely cause is
that you are not setting the same memory limit as used by the tool. Try: that you are not setting the same memory limit as used by the tool. Try:
```shell
$ LIMIT_MB=50 $ LIMIT_MB=50
$ ( ulimit -Sv $[LIMIT_MB << 10]; /path/to/tested_binary ... ) $ ( ulimit -Sv $[LIMIT_MB << 10]; /path/to/tested_binary ... )
```
Change LIMIT_MB to match the -m parameter passed to afl-fuzz. On OpenBSD, Change LIMIT_MB to match the -m parameter passed to afl-fuzz. On OpenBSD,
also change -Sv to -Sd. also change -Sv to -Sd.
Any existing output directory can be also used to resume aborted jobs; try: Any existing output directory can be also used to resume aborted jobs; try:
```shell
$ ./afl-fuzz -i- -o existing_output_dir [...etc...] $ ./afl-fuzz -i- -o existing_output_dir [...etc...]
```
If you have gnuplot installed, you can also generate some pretty graphs for any If you have gnuplot installed, you can also generate some pretty graphs for any
active fuzzing task using afl-plot. For an example of how this looks like, active fuzzing task using afl-plot. For an example of how this looks like,
see http://lcamtuf.coredump.cx/afl/plot/. see [http://lcamtuf.coredump.cx/afl/plot/](http://lcamtuf.coredump.cx/afl/plot/).
9) Parallelized fuzzing ## 9) Parallelized fuzzing
----------------------- -----------------------
Every instance of afl-fuzz takes up roughly one core. This means that on Every instance of afl-fuzz takes up roughly one core. This means that on
multi-core systems, parallelization is necessary to fully utilize the hardware. multi-core systems, parallelization is necessary to fully utilize the hardware.
For tips on how to fuzz a common target on multiple cores or multiple networked For tips on how to fuzz a common target on multiple cores or multiple networked
machines, please refer to parallel_fuzzing.txt. machines, please refer to [parallel_fuzzing.txt](docs/parallel_fuzzing.txt).
The parallel fuzzing mode also offers a simple way for interfacing AFL to other The parallel fuzzing mode also offers a simple way for interfacing AFL to other
fuzzers, to symbolic or concolic execution engines, and so forth; again, see the fuzzers, to symbolic or concolic execution engines, and so forth; again, see the
last section of parallel_fuzzing.txt for tips. last section of [parallel_fuzzing.txt](docs/parallel_fuzzing.txt) for tips.
10) Fuzzer dictionaries ## 10) Fuzzer dictionaries
---------------------- ----------------------
By default, afl-fuzz mutation engine is optimized for compact data formats - By default, afl-fuzz mutation engine is optimized for compact data formats -
@ -361,13 +372,13 @@ redundant verbiage - notably including HTML, SQL, or JavaScript.
To avoid the hassle of building syntax-aware tools, afl-fuzz provides a way to To avoid the hassle of building syntax-aware tools, afl-fuzz provides a way to
seed the fuzzing process with an optional dictionary of language keywords, seed the fuzzing process with an optional dictionary of language keywords,
magic headers, or other special tokens associated with the targeted data type magic headers, or other special tokens associated with the targeted data type
- and use that to reconstruct the underlying grammar on the go: -- and use that to reconstruct the underlying grammar on the go:
http://lcamtuf.blogspot.com/2015/01/afl-fuzz-making-up-grammar-with.html [http://lcamtuf.blogspot.com/2015/01/afl-fuzz-making-up-grammar-with.html](http://lcamtuf.blogspot.com/2015/01/afl-fuzz-making-up-grammar-with.html)
To use this feature, you first need to create a dictionary in one of the two To use this feature, you first need to create a dictionary in one of the two
formats discussed in dictionaries/README.dictionaries; and then point the fuzzer formats discussed in [dictionaries/README.dictionaries](ictionaries/README.dictionaries);
to it via the -x option in the command line. and then point the fuzzer to it via the -x option in the command line.
(Several common dictionaries are already provided in that subdirectory, too.) (Several common dictionaries are already provided in that subdirectory, too.)
@ -375,7 +386,7 @@ There is no way to provide more structured descriptions of the underlying
syntax, but the fuzzer will likely figure out some of this based on the syntax, but the fuzzer will likely figure out some of this based on the
instrumentation feedback alone. This actually works in practice, say: instrumentation feedback alone. This actually works in practice, say:
http://lcamtuf.blogspot.com/2015/04/finding-bugs-in-sqlite-easy-way.html [http://lcamtuf.blogspot.com/2015/04/finding-bugs-in-sqlite-easy-way.html](http://lcamtuf.blogspot.com/2015/04/finding-bugs-in-sqlite-easy-way.html)
PS. Even when no explicit dictionary is given, afl-fuzz will try to extract PS. Even when no explicit dictionary is given, afl-fuzz will try to extract
existing syntax tokens in the input corpus by watching the instrumentation existing syntax tokens in the input corpus by watching the instrumentation
@ -384,10 +395,10 @@ parsers and grammars, but isn't nearly as good as the -x mode.
If a dictionary is really hard to come by, another option is to let AFL run If a dictionary is really hard to come by, another option is to let AFL run
for a while, and then use the token capture library that comes as a companion for a while, and then use the token capture library that comes as a companion
utility with AFL. For that, see libtokencap/README.tokencap. utility with AFL. For that, see [libtokencap/README.tokencap](libtokencap/README.tokencap).
11) Crash triage ## 11) Crash triage
---------------- ----------------
The coverage-based grouping of crashes usually produces a small data set that The coverage-based grouping of crashes usually produces a small data set that
@ -416,7 +427,9 @@ beneath.
Oh, one more thing: for test case minimization, give afl-tmin a try. The tool Oh, one more thing: for test case minimization, give afl-tmin a try. The tool
can be operated in a very simple way: can be operated in a very simple way:
```shell
$ ./afl-tmin -i test_case -o minimized_result -- /path/to/program [...] $ ./afl-tmin -i test_case -o minimized_result -- /path/to/program [...]
```
The tool works with crashing and non-crashing test cases alike. In the crash The tool works with crashing and non-crashing test cases alike. In the crash
mode, it will happily accept instrumented and non-instrumented binaries. In the mode, it will happily accept instrumented and non-instrumented binaries. In the
@ -431,10 +444,10 @@ file, attempts to sequentially flip bytes, and observes the behavior of the
tested program. It then color-codes the input based on which sections appear to tested program. It then color-codes the input based on which sections appear to
be critical, and which are not; while not bulletproof, it can often offer quick be critical, and which are not; while not bulletproof, it can often offer quick
insights into complex file formats. More info about its operation can be found insights into complex file formats. More info about its operation can be found
near the end of technical_details.txt. near the end of [docs/technical_details.txt](docs/technical_details.txt).
12) Going beyond crashes ## 12) Going beyond crashes
------------------------ ------------------------
Fuzzing is a wonderful and underutilized technique for discovering non-crashing Fuzzing is a wonderful and underutilized technique for discovering non-crashing
@ -455,11 +468,11 @@ found by modifying the target programs to call abort() when, say:
Implementing these or similar sanity checks usually takes very little time; Implementing these or similar sanity checks usually takes very little time;
if you are the maintainer of a particular package, you can make this code if you are the maintainer of a particular package, you can make this code
conditional with #ifdef FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION (a flag also conditional with `#ifdef FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION` (a flag also
shared with libfuzzer) or #ifdef __AFL_COMPILER (this one is just for AFL). shared with libfuzzer) or `#ifdef __AFL_COMPILER` (this one is just for AFL).
13) Common-sense risks ## 13) Common-sense risks
---------------------- ----------------------
Please keep in mind that, similarly to many other computationally-intensive Please keep in mind that, similarly to many other computationally-intensive
@ -485,10 +498,12 @@ tasks, fuzzing may put strain on your hardware and on the OS. In particular:
A good way to monitor disk I/O on Linux is the 'iostat' command: A good way to monitor disk I/O on Linux is the 'iostat' command:
```shell
$ iostat -d 3 -x -k [...optional disk ID...] $ iostat -d 3 -x -k [...optional disk ID...]
```
14) Known limitations & areas for improvement ## 14) Known limitations & areas for improvement
--------------------------------------------- ---------------------------------------------
Here are some of the most important caveats for AFL: Here are some of the most important caveats for AFL:
@ -509,33 +524,34 @@ Here are some of the most important caveats for AFL:
experimental/post_library/ (with AFL_POST_LIBRARY) experimental/post_library/ (with AFL_POST_LIBRARY)
- There are some unfortunate trade-offs with ASAN and 64-bit binaries. This - There are some unfortunate trade-offs with ASAN and 64-bit binaries. This
isn't due to any specific fault of afl-fuzz; see notes_for_asan.txt for isn't due to any specific fault of afl-fuzz; see [docs/notes_for_asan.txt](docs/notes_for_asan.txt)
tips. for tips.
- There is no direct support for fuzzing network services, background - There is no direct support for fuzzing network services, background
daemons, or interactive apps that require UI interaction to work. You may daemons, or interactive apps that require UI interaction to work. You may
need to make simple code changes to make them behave in a more traditional need to make simple code changes to make them behave in a more traditional
way. Preeny may offer a relatively simple option, too - see: way. Preeny may offer a relatively simple option, too - see:
https://github.com/zardus/preeny [https://github.com/zardus/preeny](https://github.com/zardus/preeny)
Some useful tips for modifying network-based services can be also found at: Some useful tips for modifying network-based services can be also found at:
https://www.fastly.com/blog/how-to-fuzz-server-american-fuzzy-lop [https://www.fastly.com/blog/how-to-fuzz-server-american-fuzzy-lop](https://www.fastly.com/blog/how-to-fuzz-server-american-fuzzy-lop)
- AFL doesn't output human-readable coverage data. If you want to monitor - AFL doesn't output human-readable coverage data. If you want to monitor
coverage, use afl-cov from Michael Rash: https://github.com/mrash/afl-cov coverage, use afl-cov from Michael Rash: [https://github.com/mrash/afl-cov](https://github.com/mrash/afl-cov)
- Occasionally, sentient machines rise against their creators. If this - Occasionally, sentient machines rise against their creators. If this
happens to you, please consult http://lcamtuf.coredump.cx/prep/. happens to you, please consult [http://lcamtuf.coredump.cx/prep/](http://lcamtuf.coredump.cx/prep/).
Beyond this, see INSTALL for platform-specific tips. Beyond this, see INSTALL for platform-specific tips.
15) Special thanks ## 15) Special thanks
------------------ ------------------
Many of the improvements to afl-fuzz wouldn't be possible without feedback, Many of the improvements to the original afl wouldn't be possible without
bug reports, or patches from: feedback, bug reports, or patches from:
```
Jann Horn Hanno Boeck Jann Horn Hanno Boeck
Felix Groebert Jakub Wilk Felix Groebert Jakub Wilk
Richard W. M. Jones Alexander Cherepanov Richard W. M. Jones Alexander Cherepanov
@ -575,18 +591,17 @@ bug reports, or patches from:
Rene Freingruber Sergey Davidoff Rene Freingruber Sergey Davidoff
Sami Liedes Craig Young Sami Liedes Craig Young
Andrzej Jackowski Daniel Hodson Andrzej Jackowski Daniel Hodson
```
Thank you! Thank you!
16) Contact ## 16) Contact
----------- -----------
Questions? Concerns? Bug reports? The contributors can be reached via Questions? Concerns? Bug reports? The contributors can be reached via
https://github.com/vanhauser-thc/AFLplusplus [https://github.com/vanhauser-thc/AFLplusplus](https://github.com/vanhauser-thc/AFLplusplus)
There is also a mailing list for the afl project; to join, send a mail to There is also a mailing list for the afl project; to join, send a mail to
<afl-users+subscribe@googlegroups.com>. Or, if you prefer to browse <afl-users+subscribe@googlegroups.com>. Or, if you prefer to browse
archives first, try: archives first, try: [https://groups.google.com/group/afl-users](https://groups.google.com/group/afl-users)
https://groups.google.com/group/afl-users

2
afl-fuzz.c
View File

@ -23,7 +23,9 @@
#define AFL_MAIN #define AFL_MAIN
#define MESSAGES_TO_STDOUT #define MESSAGES_TO_STDOUT
#ifndef _GNU_SOURCE
#define _GNU_SOURCE #define _GNU_SOURCE
#endif
#define _FILE_OFFSET_BITS 64 #define _FILE_OFFSET_BITS 64
#include "config.h" #include "config.h"

6
llvm_mode/README.llvm
View File

@ -205,10 +205,8 @@ post-process the assembly or install any compiler plugins. See:
http://clang.llvm.org/docs/SanitizerCoverage.html#tracing-pcs-with-guards http://clang.llvm.org/docs/SanitizerCoverage.html#tracing-pcs-with-guards
As of this writing, the feature is only available on SVN trunk, and is yet to If you have a sufficiently recent compiler and want to give it a try, build
make it to an official release of LLVM. Nevertheless, if you have a afl-clang-fast this way:
sufficiently recent compiler and want to give it a try, build afl-clang-fast
this way:
AFL_TRACE_PC=1 make clean all AFL_TRACE_PC=1 make clean all

2
types.h
View File

@ -78,7 +78,7 @@ typedef int64_t s64;
#define STRINGIFY(x) STRINGIFY_INTERNAL(x) #define STRINGIFY(x) STRINGIFY_INTERNAL(x)
#define MEM_BARRIER() \ #define MEM_BARRIER() \
asm volatile("" ::: "memory") __asm__ volatile("" ::: "memory")
#if __GNUC__ < 6 #if __GNUC__ < 6
#define likely(_x) (_x) #define likely(_x) (_x)