fuzz: add plist writer API fuzzer - #316
Open
JeewoongKim wants to merge 1 commit into
Open
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
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 PR adds a new fuzz target for libplist's serializer (writer) API.
The existing fuzz targets mainly exercise parser entry points and free the parsed
plist tree. This target complements them by parsing input with
plist_from_memory()and then exercisingplist_write_to_string()with anoutput format and writer options selected from trailing input bytes.
PLIST_FORMAT_BINARYis intentionally excluded becauseplist_write_to_string()does not handle binary output.Validation:
confirmed additional writer-path coverage.
After this is merged, I will send a follow-up PR to google/oss-fuzz to enable this target
in the libplist OSS-Fuzz build.