Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added first fuzzer with oss-fuzz build script #306

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AdamKorcz
Copy link

This PR adds a fuzzer and a build script to integrate Pelikan with oss-fuzz for continuous fuzzing.

The fuzzer is implemented by way of LibFuzzer. Fuzzing is a way of testing programs whereby pseudo-random data is passed to a target function with the goal of finding bugs and vulnerabilities. Continuous fuzzing contributes to this in several ways, some of which are:

  1. Some harder-to-find bugs take longer to find, and there have been examples of bugs having been found after several CPU years of continuous fuzzing.
  2. It ensures that the fuzzers are actually run occassionally. Often effort is put into writing the fuzzers, and afterwards they are rarely run if at all.

By setting up continuous fuzzing through oss-fuzz, maintainers are notified if and when bugs are found. Notifications include detailed reports with stacktraces and test cases. oss-fuzz is a free service for open source projects that is offered with an implied expectation that bugs are fixed, so that the resources spent on fuzzing Pelikan are put to good use.

I have the build scripts for the oss-fuzz side as well and will be happy to complete the integration.

The location of the fuzzer and the oss-fuzz build script in the test/fuzz dir is a suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant