Hi there, I played around with afl-fuzz for a bit and chose ledger (https://github.com/ledger/ledger) as my "victim", since I use it for parsing my financial stuff.
The following 7-byte ledger file causes a segfault for me: ###start file### =\n ~\n 00 ###end file### (there is no newline at the end of the file, it still segfaults with a newline though) To reproduce, I just run "ledger -f crash.ledger source" and get a segfault, it might be interesting for you to debug this further. Also I doubt that many people run ledger with the --verify switch - which means that they'll get a buffer overflow as soon as they execute a file with dates that are longer than 127 characters... Maybe the speed reduction of checking that the string really is short enough might be worth it in that case? Otherwise please make it more clear that not using --verify on ANY ledger file that you have not closely examined might lead to issues. Cheers, Markus -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
