boost: add new fuzzers #11477
Merged
boost: add new fuzzers #11477
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
TheZ3ro is a new contributor to projects/boost. The PR must be approved by known contributors before it can be merged. The past contributors are: Navidem, inferno-chromium, Dor1s, bshastry (unverified), pauldreik (unverified), kcc, nevir (unverified) |
DonggeLiu
approved these changes
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request add multiple fuzzer harnesses for various Boost libraries, namely:
Boost.Datetime, Boost.Graph, Boost.Regex, Boost.Filesystem, Boost.ProgramOptions, and Boost.UUID.
The PR also adds some seed corpus for GraphML and GraphViz files used by the Boost.Graph harness.
The fuzzers are temporary committed in oss-fuzz, but we are in touch with upstream maintainers to add the harnesses directly in their repositories.
Sadly the Boost ecosystem is heavily fragmented so this process will take some time.
The fuzzers already lead to multiple crashes triaged by upstream maintainers so we think this would be the best approach.
Thanks