| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
* [cryptofuzz] wolfCrypt: Build with mp_jacobi
* [cryptofuzz] wolfCrypt: Support Ed25519, Ed448
|
|
|
| |
Signed-off-by: Peter Hillman <peter@pedro.kiwi>
|
|
|
|
|
|
|
|
|
|
|
| |
Coverage builds need to be special cased since they aren't specified
in sanitizers. Instead they are done for all C/C++ projects that
use libFuzzer.
Move all of this special casing to `should_build_coverage` and call that from
`should_build` so we have one place where we decide this.
Add tests as well.
Fixes: https://github.com/google/oss-fuzz/issues/4371
|
|
|
|
| |
It's broken now because ClusterFuzz's blackbox fuzzer model can't
support it.
|
|
|
|
|
| |
* [quic-go] add a fuzz target for tokens
* [quic-go] generate seed corpora in build script
|
| |
|
| |
|
|
|
| |
'none' is used by projects like spidermonkey that use the JS fuzzer.
|
|
|
|
|
|
|
|
|
| |
(#4338). (#4367)
* [infra] Fix reproduce command invoking run_fuzzer for a single testcase (#4338).
* review feedback
* do not introduce new variable, rely on SKIP_SEED_CORPUS only
|
| |
|
|
|
|
| |
configuration (#4358)
|
| |
|
| |
|
|
|
| |
Temporarily fixes #4348
|
|
|
|
|
| |
(#4351)" (#4352)
This reverts commit 7f8f5e0182ec994ed5b7340cdf90c532da1ee328.
|
|
|
| |
This reverts commit d1ddd259378933ab42966da3e6750612c3ec2de4.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* initial commit
* update build script, build failing
* add necessary environment variable definitions
* build working
* programmatically get system bits
* add md5 fuzzer
* fix style
* add fuzzers for two more hash functions
* testing dynamic includes
* build working
* clean up build script
* add aes fuzzer
* patch block_common to avoid build issues
* remove comments
* update patchfile location
* move patchfile again
* apply patch from subdirectory
* remove another comment
* change state type, use same data for encryption and decryption
|
| |
|
| |
|
| |
|
|
|
|
| |
This change adds me (Kalvin) to the list of contributors allowed
to view Ghostscript issues on OSS-Fuzz.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* initial commit
* update build script, build failing
* add necessary environment variable definitions
* build working
* programmatically get system bits
* add md5 fuzzer
* fix style
* add fuzzers for two more hash functions
* testing dynamic includes
* build working
* clean up build script
* style fixes
|
|
|
|
|
|
|
| |
* [infra] Upgrade reproduce command to re-use run_fuzzer functionality.
* fix a typo
* add missing quotes
|
|
|
|
|
| |
- Add new XPath fuzz target
- Set V=1 globally
- Clean seed corpus to make sure it will be rebuilt
|
|
|
|
|
|
|
| |
* Build of nodejs has now been upstreamed and this commit simplifies the build for nodejs to the new updates.
* We only support libfuzzer for now.
* Simplified the build script.
|
|
|
|
| |
project configuration (#4328)
|
|
|
| |
Signed-off-by: Asra Ali <asraa@google.com>
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* merge a new fuzzer o
* merge a new fuzzer of usrsctp
|
|
|
|
|
|
| |
Do this so that CIFuzz will work.
Co-authored-by: Zepeng Hu <zepenghu@google.com>
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
|
|
|
|
|
| |
* [infra] Use 16 threads when building LLVM (#4270).
* update the comment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Get Sleuthkit building in the OSS-Fuzz builder.
* added fuzzers, included primary contact email, and updated build script
* included license headers
* fixed variable name typo in build script
* remove memory initialization in sleuthkit_mem_img.h
* style fixes, remove instances of goto
Co-authored-by: Ravi Jotwani <rjotwani@google.com>
|
|
|
|
| |
change the primary contact to the BIND 9 developers group alias,
instead of security-officer
|
| |
|
|
|
|
|
|
| |
Hopefully this should prevent OSS-Fuzz from reporting bugs that
have alread been fixed. Though I'm not sure how stable it's going to be
given that https://github.com/google/oss-fuzz/issues/4083 is still
open. Let's see.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* added draco integration files
* wrote build file and Dockerfile for Draco
* added more fuzzers, updated build script to generate corpus and options for each
* place yaml.dict in SRC first, rather than in OUT directly
* changed fuzzers from c++ to c, updated build script
* started using booleans instead of ints, updated naming conventions
* replaced all instances of with
* removed memsets, stopped using first two bytes of input, and removed file I/O
* fixed style, changed function return types to bool instead of int
* added libyaml_parser_fuzzer back, implemented string handling to not exceed buffer size in libyaml_emitter_fuzzer, and made style fixes
* changed boolean functions to return error, not success
* fixed inverted check
* changed variable names, fixed crash in libyaml_emitter_fuzzer
* fixed addition/subtraction style
* make a dynamically growing heap buffer
* place yaml_write_handler in distinct header file, style fixes
* fix style and memory safety issues in reformatter fuzzers, remove unused vars
* consistent assignment of done variables
|
|
|
|
|
|
|
|
|
| |
Deleting this fuzzer as it has proved problematic (see internal bug #160587918). Reasons for deletion:
- This fuzzer is not written well. We pass an uninitialized output buffer to `ext2fs_read_dir_block()`, have redundant function calls (see [here](https://github.com/tytso/e2fsprogs/blob/master/lib/ext2fs/dirblock.c#L62) and [here](https://github.com/google/oss-fuzz/blob/d36af019b0a5c4e05f7e644250a46809571f977d/projects/e2fsprogs/fuzz/ext2fs_read_write_dir_block_fuzzer.cc#L66)), and pass empty `blk64_t` structs to the fuzz targets.
- Removing this fuzzer has negligible impact on total coverage. Running [this](https://github.com/googleinterns/oss-fuzz-utils/blob/master/coverage.sh) coverage utility after removing the fuzzer locally outputs the following results (fuzzing each build for 10 minutes).
```original: 244/13082 regions - 1.86515823269% coverage
modified: 239/13070 regions - 1.8286151492% coverage```
@tytso @alsophian Please feel free to chime in.
|
| |
|
|
|
| |
Co-authored-by: Joe Drago <jdrago@netflix.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [CRAS] Fix build error and build new fuzzer
- Fix build error by installing 1.8.x gtest and using `make install` to
install gtest pc file for pkg-config
- Build and add new fuzzer `cras_hfp_slc`
BUG=oss-fuzz:24744
* fix the copyright
* fix the copyright
* Update Dockerfile
Co-authored-by: Max Moroz <mmoroz@chromium.org>
|