-
Notifications
You must be signed in to change notification settings - Fork 238
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
Crashes found with afl #30
Comments
There was a change made recently, how many of these crash cases still exist? |
Probably most of them. cJSON is in quite bad shape in this regard. Many crashes can probably eliminated by fixing cJSONs unicode handling. |
246 of 246 still exist on tips of master as of a few minutes ago. |
Program received signal SIGABRT, Aborted. |
Just FYI, the official repo at https://github.com/daveGamble/cJSON has all these fixed. |
Thanks for the tip Dave. |
Wow, I've been running Afl for one night and didn't find any crashes anymore. Nice Job @DaveGamble, I'm really impressed. I've been trying to fix some of these by myself, but every time I fixed one problem, it reappeared somewhere else. Afl found one hang, but I still have to find out if it is legitimate. I'll be doing this in the evening I guess (GMT+7). |
The hang is a false positive 👍 |
Please contact me for 246 crash cases found by fuzzing with afl. It's likely there aren't 246 actual errors, just 246 ways to get to the same few. These issues should be treated as critical since JSON parsing is often exposed on the attack surface.
The text was updated successfully, but these errors were encountered: