commit | aab2e82b4acfb37ba5cbc9ffb89481d316fe5193 | [log] [tgz] |
---|---|---|
author | jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com> | Fri Feb 26 10:22:32 2021 -0800 |
committer | GitHub <noreply@github.com> | Fri Feb 26 18:22:32 2021 +0000 |
tree | b2d07ab61c24777f685f73f606d7266571a21fa1 | |
parent | 98a2db88c4f4d95728bc8af7494ccf5cd798edc2 [diff] |
[jazzer][java-example] Fix native library loading. (#5262) Prior to this change, native library loading failed for two reasons: 1. Loading from current working directory instead of the fuzzer's directory. 2. Using ASAN_OPTIONS=handle_segv=2. Fix these issues by doing the following. 1. Adding the fuzzer's directory to LD_LIBRARY_PATH instead of "." 2. Specifying handle_segv=1 in ASAN_OPTIONS. Related: https://github.com/google/oss-fuzz/issues/5178
Fuzz testing is a well-known technique for uncovering programming errors in software. Many of these detectable errors, like buffer overflow, can have serious security implications. Google has found thousands of security vulnerabilities and stability bugs by deploying guided in-process fuzzing of Chrome components, and we now want to share that service with the open source community.
In cooperation with the Core Infrastructure Initiative and the OpenSSF, OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques with scalable, distributed execution.
We support the libFuzzer, AFL++, and Honggfuzz fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.
Currently, OSS-Fuzz supports C/C++, Rust, Go and Python code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.
Read our detailed documentation to learn how to use OSS-Fuzz.
As of January 2021, OSS-Fuzz has found over 25,000 bugs in 375 open source projects.