Add libFuzzer harnesses for the pure hostile-input parsers - #500
Closed
xroche wants to merge 1 commit into
Closed
Conversation
xroche
force-pushed
the
fix-parser-fuzz-bugs
branch
from
July 7, 2026 06:42
6568124 to
8b676d4
Compare
xroche
force-pushed
the
p3-1-fuzzers
branch
2 times, most recently
from
July 7, 2026 06:44
397ee59 to
96949b2
Compare
xroche
force-pushed
the
fix-parser-fuzz-bugs
branch
from
July 7, 2026 07:03
8b676d4 to
559c88f
Compare
xroche
force-pushed
the
fix-parser-fuzz-bugs
branch
from
July 7, 2026 13:15
559c88f to
c675050
Compare
xroche
force-pushed
the
p3-1-fuzzers
branch
2 times, most recently
from
July 7, 2026 16:02
dcd38fe to
b039e22
Compare
New fuzz/ tree with a libFuzzer harness per pure (buf,size) parser that ingests network-sourced bytes: the charset/UTF-8/IDNA codecs, the HTML <meta> charset scan, HTML entity and URL percent decoders, the wildcard filter matcher, and the URL splitter. Gated behind --enable-fuzzers (requires clang, forces --disable-shared so clang's static sanitizer runtimes link); a normal build is untouched. A CI job builds the harnesses under ASan+UBSan+LeakSanitizer and replays each seed corpus. Replay, not open-ended mutation, keeps the job deterministic and avoids strjoker's catastrophic backtracking (a data-dependent exponential in the wildcard matcher, tracked separately). Maintainers run the timed mutation mode locally for discovery; OSS-Fuzz is the next step. The corpora carry the reproducers for the four parser bugs these harnesses found, so the job also pins those regressions. It depends on the fixes in the preceding commit; merge that first. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Xavier Roche <roche@httrack.com>
xroche
force-pushed
the
fix-parser-fuzz-bugs
branch
from
July 7, 2026 16:05
c675050 to
9a63b4a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A
fuzz/tree with one libFuzzer harness per pure(buf, size)parser that ingests network bytes: the charset, UTF-8, and IDNA codecs, the<meta>charset scan, the entity and URL percent decoders, the filter matcher, and the URL splitter. It sits behind--enable-fuzzers(needs clang, forces--disable-shared), so a normal build is untouched.A CI job builds them under ASan, UBSan, and LeakSanitizer and replays each seed corpus. Replaying keeps it deterministic and avoids
strjoker's catastrophic backtracking, tracked in #501. The corpora carry the reproducers for the four parser bugs found here, so the job pins those regressions.Stacked on #499; merge that one first.