Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / honggfuzz / 2036e20d44d1b8b5e945c1f4d2767496a628e53a
commit2036e20d44d1b8b5e945c1f4d2767496a628e53a[log] [tgz]
authorRobert Swiecki <robert@swiecki.net>Tue Jun 06 00:01:44 2017 +0200
committerRobert Swiecki <robert@swiecki.net>Tue Jun 06 00:01:44 2017 +0200
treeb1431fde6a33a62c0ed24248181d8bdb2a3c5a5f
parent2af83ec79fb752d82cb0e21ee1d6841254610dbb [diff]
subproc: use non-blocking socket to send persistent data
3 files changed
tree: b1431fde6a33a62c0ed24248181d8bdb2a3c5a5f
  1. android/
  2. docs/
  3. examples/
  4. hfuzz_cc/
  5. libcommon/
  6. libhfuzz/
  7. linux/
  8. mac/
  9. posix/
  10. third_party/
  11. tools/
  12. .gitignore
  13. .gitmodules
  14. arch.h
  15. CHANGELOG
  16. cmdline.c
  17. cmdline.h
  18. CONTRIBUTING
  19. COPYING
  20. display.c
  21. display.h
  22. fuzz.c
  23. fuzz.h
  24. honggfuzz.c
  25. Makefile
  26. mangle.c
  27. mangle.h
  28. README.md
  29. report.c
  30. report.h
  31. sancov.c
  32. sancov.h
  33. sanitizers.c
  34. sanitizers.h
  35. subproc.c
  36. subproc.h
README.md

honggfuzz

Description

A security oriented, feedback-driven, evolutionary, easy-to-use fuzzer with interesting analysis options. See USAGE for more data on the usage.

  • It's multi-threaded and multi-process: no need to run multiple copies of your fuzzer, as honggfuzz can unlock potential of all your available CPU cores. The file corpus is shared between threads (and fuzzed instances)
  • It's blazingly fast (esp. in the persistent fuzzing mode). A simple LLVMFuzzerTestOneInput function can be tested with up to 1mo iterations per second on a relatively modern CPU (e.g. i7-6600K)
  • Has a nice track record of uncovered security bugs: e.g. the only (to the date) vulnerability in OpenSSL with the critical score mark was discovered by honggfuzz
  • Uses low-level interfaces to monitor processes (e.g. ptrace under Linux). As opposed to other fuzzers, it will discover and report hidden signals (caught and potentially hidden by signal handlers)
  • Easy-to-use, feed it a simple input corpus (can even consist of a single, 1-byte file) and it will work its way up expanding it utilizing feedback-based coverage metrics
  • Supports several (more than any other coverage-based feedback-driven fuzzer) hardware-based (CPU: branch/instruction counting, Intel BTS, Intel PT) and software-based feedback-driven fuzzing methods known from other fuzzers (libfuzzer, afl)
  • Works (at least) under GNU/Linux, FreeBSD, Mac OS X, Windows/CygWin and Android
  • Supports persistent fuzzing mode (long-lived process calling a fuzzed API repeatedly) with libhfuzz/libhfuzz.a. More on that can be found here
  • Can fuzz remote/standalone long-lasting processes (e.g. network servers like Apache's httpd and ISC's bind)
  • It comes with the examples directory, consisting of real world fuzz setups for widely-used software (e.g. Apache and OpenSSL)

Code

  • Latest stable version: 1.0, but using the master branch is highly encouraged
  • Changelog

Requirements

  • Linux - The BFD library (libbfd-dev) and libunwind (libunwind-dev/libunwind8-dev), clang-4.0 or higher for software-based coverage modes
  • FreeBSD - gmake, clang-3.6 or newer (clang-devel/4.0 suggested)
  • Android - Android SDK/NDK. Also see this detailed doc on how to build and run it
  • Windows - CygWin
  • Darwin/OS X - Xcode 10.8+
  • if Clang/LLVM is used to compile honggfuzz - link it with the BlocksRuntime Library (libblocksruntime-dev)

Trophies

Honggfuzz has been used to find a few interesting security problems in major software packages; An incomplete list:

Projects utilizing Honggfuzz

Examples

The examples directory contains code demonstrating (among others) how to use honggfuzz to find bugs in the OpenSSL library and in the Apache web server.

Other

This is NOT an official Google product.