Age | Commit message (Collapse) | Author |
|
The JVM uses custom SIGSEGV handlers, which leads to fuzzer crashes on
ClusterFuzz when running with ASAN likely due to the
allow_user_segv_handler=1 default on the platform.
|
|
add maintainer email
|
|
|
|
|
|
|
|
|
|
|
|
invoked from build.sh. (#5548)
|
|
|
|
|
|
|
|
|
|
Previously the allocator handled small pointer values incorrectly
and prevented multiple executions (unexpectedly used when OSS-fuzz
uses LSAN to look for memory leaks).
|
|
|
|
|
|
|
|
Now that https://github.com/lxc/lxc/pull/3733 is merged, it should be
safe to point OSS-Fuzz to the lxc repository.
|
|
* Adds project openbabel
* fixup target merged upstream
|
|
|
|
|
|
|
|
* Adds structure-aware target for suricata
* Remove rustc wrapper for suricata
now that https://github.com/rust-lang/rust/issues/82144
got fixed
* Remove suricata rust workarounds for coverage
Now that https://github.com/rust-lang/rust/issues/82144
got fixed
|
|
Fixes #5513
|
|
|
|
|
|
libjpeg-turbo 2.1 now requires NASM 2.13 or later or YASM 1.2.0 or
later. Since the Docker image is based on Ubuntu 16.04, NASM 2.13 isn't
available, so the easiest workaround is to use YASM instead.
Fixes #4931
|
|
In bytecodealliance/rfcs#10, we have outlined a process by which we're
switching to a new compiler backend by default. The first step in this
process is to switch our fuzzing targets to use the new backend and wait
for any issues.
This PR adds the Cargo feature that enables the new backend in all
fuzzing targets.
|
|
The other two mail addresses are aliases and so we can't use them to
access oss-fuzz.
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
|
|
|
|
|
|
Previously the allocator handled small pointer values incorrectly
and prevented multiple executions (unexpectedly used when OSS-fuzz
uses LSAN to look for memory leaks). More over there were cases
where too large allocations were not caught and the allocator
needlessly kept track of peak allocation statistics.
|
|
This makes it easier to build the fuzzer using a locally checked
out git repo without having to manually copy the fuzzer glue code
into the locally checked out git repo first.
|
|
- Enable i386 fuzzing
- Enable more operations (Digest, HMAC, KDF_X963, ECC_ValidatePubkey)
- Scope the calc operations in order to spend less time trying to run calculations not supported by relic
- Compile Botan module in oracle mode: makes it more likely to find discrepancies
|
|
added in https://github.com/Geal/nom/commit/0a499cd123cca25bd48d243c0109147c7627f155
|
|
MAP_ANONYMOUS, getpagesize and strnlen do not mix with c99.
Updates #32432 "wuffs: Fuzzing build failure"
|
|
This should fix coverage build broken again today. It seems that a
recent change in TF toolchains removed the creation of `org_tensorflow`
but it is likely that this change will be rolled back in the future.
Hence, to keep OSSFuzz working, we conditionally remove this symlink.
|
|
We don't do any internal tests using honggfuzz, and our code is highly
unlikely to work with honggfuzz in the current shape. All of the
true-positive bugs seem to be libfuzzer bugs.
Lets disable honggfuzz, to avoid wasting resources. We will try to get
afl++ working, before taking another look at honggfuzz.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
|
|
|
|
|
|
|
|
Also, update base-builder version.
Fixes: #3157
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* output afl++ setup
* update commit id
* update afl++ commit id
* asan + cmplog fix
* update commit id
* update and enhance afl++
* update afl++ commit id, better run asan options
* fix linter
* add debug_afl script
* Update debug_afl
* Update compile_afl
* fix for karchive
* put debug_afl in the docker container
* asan poison fix
* fix asan settings for zeek
* update afl++ commit id
* fix
* update afl++ commit id
* final touches
* remove map size
* remove old comment
* llvm 13 fix
* enhance documentation
* fix capstone build.sh
* update doc
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
|