The libfuzzer-sys
Crate
Barebones wrapper around LLVM's libFuzzer runtime library.
The CPP parts are extracted from compiler-rt git repository with git filter-branch
.
libFuzzer relies on LLVM sanitizer support. The Rust compiler has built-in support for LLVM sanitizer support, for now, it's limited to Linux. As a result, libfuzzer-sys
only works on Linux.
Usage
Use cargo fuzz
!
The recommended way to use this crate with cargo fuzz
!.
Manual Usage
This crate can also be used manually as following:
First create a new cargo project:
$ cargo new --bin fuzzed
$ cd fuzzed
Then add a dependency on the fuzzer-sys
crate and your own crate:
[]
= "0.4.0"
= { = "../path/to/your/crate" }
Change the fuzzed/src/main.rs
to fuzz your code:
use fuzz_target;
fuzz_target!;
Build by running the following command:
And finally, run the fuzzer:
Linking to a local libfuzzer
When using libfuzzer-sys
, you can provide your own libfuzzer
runtime in two ways.
If you are developing a fuzzer, you can set the CUSTOM_LIBFUZZER_PATH
environment variable to the path of your local
libfuzzer
runtime, which will then be linked instead of building libfuzzer as part of the build stage of libfuzzer-sys
.
For an example, to link to a prebuilt LLVM 16 libfuzzer
, you could use:
Alternatively, you may also disable the default link_libfuzzer
feature:
In Cargo.toml
:
[]
= { = "../../libfuzzer", = false }
Then link to your own runtime in your build.rs
.
Updating libfuzzer from upstream
-
Update the
COMMIT=...
variable in./update-libfuzzer.sh
with the new commit hash from llvm-mirror/llvm-project that you are vendoring. -
Re-run the script:
$ ./update-libfuzzer.sh <github.com/llvm-mirror/llvm-project SHA1>
License
All files in the libfuzzer
directory are licensed NCSA.
Everything else is dual-licensed Apache 2.0 and MIT.