-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various panics found through go-fuzz #15
Comments
Thanks! I'll shore up the library as I find time in the coming few days! |
Addresses the crashes found in #15, and a couple more.
(I'm now using go-fuzz, starting with your crashers and a corpus of valid property lists. Thanks so much for the report/s.) |
A fair few of these are fixed, thanks to you reporting this. There are a couple crashers in |
I'm leaving the issue open as a discussion and placeholder for future fuzzing issues. |
Fixes some crashes found via fuzzing; refs #15.
After all of the above fixes, I ran go-fuzz for ~25 minutes and didn't hit any more crashers other than #23, which will require a minor architectural change to fix. Thanks again, @akrennmair! |
Hi,
Just wanted to let you that I tested go-plist using go-fuzz and the following code snippet:
The tool found several panics. In order to reproduce this, you can find the files here in my Google Drive: https://drive.google.com/file/d/0B8eVqk16QdZ6Y21mTm8zZnVGZlE/view
The .output files contain the respective stack traces. The file without any suffix contains the actual data fed to the Fuzz function. The .quoted file contains the file content as string that is usable in unit tests.
The text was updated successfully, but these errors were encountered: