test: add libFuzzer harness for rrd_restore - #1372
Open
somethingwithproof wants to merge 3 commits into
Open
Conversation
Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1372 +/- ##
==========================================
+ Coverage 51.21% 51.65% +0.43%
==========================================
Files 45 45
Lines 18372 18420 +48
==========================================
+ Hits 9410 9514 +104
+ Misses 8962 8906 -56 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Extends the existing rrd_open fuzz harness (#1368) to rrd_restore's XML
parsing path -- the original ask named both as fuzz targets, only
rrd_open was covered. Opt-in via --enable-fuzzing, not part of the
default build or make check.
Found a real, independently-confirmed heap-buffer-overflow read within
a 30s smoke run using only the seed corpus -- fixed separately in #1371,
which also has the before/after verification. The crash-triggering
fixture is kept in the corpus here as a regression seed.