Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Potentially security-sensitive crashes, best way to get them to you? #235
I have been fuzzing libical for a while, I have a handful of use-after-frees (might be all the same root bug) I would like to provide, but these are potentially security-sensitive and not appropriate for a github comment.
An example asan trace (tested against 1.0, 1.0.1?, and master from 20 minutes ago):
What's the best way to get the test cases to reproduce the issues to you? My email is email@example.com if you would like to hit me up directly at your convenience.