-
Notifications
You must be signed in to change notification settings - Fork 23
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
Most implementations have low tolerance to corrupted database files #46
Comments
Ping ? It's been a month :) |
Thanks for the report (and sorry for the belated response). Let me know of the goal of this experiment. |
The expected behaviour is not to crash, at the very least :) For the record:
|
Hello,
tkrzw_crashes_202404_01.tar.gz
Here's a tarball containing a set of redundant corrupted files which crash at least one of the commands listed below, and the corresponding terminal output (crashes_*.txt files):
in tkrzw 1.0.27 built thusly under Debian sid amd64:
Most of the crashes on those files are controlled asserts caused by attempts to allocate terabytes of memory or more; however, there are also wild pointer accesses, heap-based buffer overflows, etc.
Only the
tkh
file type didn't fall to afl-fuzz (yet);tkmb tkmc tkmt tks tksh tkst tkt
did, most of them for all five commands, often within the first few seconds of fuzzing, if not the first dozens of milliseconds. Some of them reached ~2% crash rate.FTR:
The initial corpus of valid files was built by
afl-fuzz
invocations:I then massaged the output folders for easier use on the maintainer side :)
The text was updated successfully, but these errors were encountered: