[Fuzzing] Add fuzzing harness for HTTP3Frame
#11128
Merged
Conversation
This file contains hidden or 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
Co-Authored-By: Yannis Hofmann <yannis.hofmann@student.hpi.de>
Contributor
Author
|
We've verified this to work locally by manually building + running the tracer using the |
Contributor
Author
|
The failing test seems unrelated to me. |
Contributor
|
[approve ci autest] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The
proxy/http3package isn't covered by fuzz tests at all currently. Since HTTP3 is interfaced directly with the user-agent, it's a prime attack target.This PR contributes a fuzzing setup for the
HTTP3Frameparser. In depends on the H3 tools to compile, so we've extendedoss-fuzz.shto run the existing utility script.