fix: triage and create issues for fuzzer findings (April 2024 edition)

[terriko]

• related: Follow up on fuzzing reports #3800

We've added a bunch of new fuzzers so it's time to go through our fuzzing findings again!

You can see the jobs that ran here:
https://github.com/intel/cve-bin-tool/actions/workflows/fuzzing.yml

The ones of interest here are likely the ones that failed in less than an hour (all of our fuzzing jobs give up after an hour and will be marked as failed by github actions as a result).

Steps:

1. Find a fuzzer run with an interesting failure in the list: https://github.com/intel/cve-bin-tool/actions/workflows/fuzzing.yml
2. File an issue with an appropriate snippet of the log showing what the failure was. (We don't have a fuzz issue template yet, but you can use a bug template or a blank one.)
3. (Optional) Make a PR to fix the issue.

Since a lot of these fuzzers are pretty new, I expect a lot of the issues found will be fairly basic data validation issues right now, but you never know -- you might find a real security issue!

[joydeep049]

Hello @terriko
I would like to take this up.

[terriko]

@joydeep049 have fun! there's enough interesting-looking stuff in there at a glance that probably more than one person could work on this, so you might wnat to file an issue saying which one you're investigating as described above.

[joydeep049]

@terriko You're right this is so much fun!
I already filed some issues related to it!

[joydeep049]

This is another problem that I encountered while analysing fuzz report https://github.com/intel/cve-bin-tool/actions/runs/7955755310
Is this one worth filing? Because this problem wasnt encountered in any other report.
Network Issue maybe???
@terriko @anthonyharrison

[joydeep049]

This UNABLE TO OPEN DATABASE problem occurred in a few reports.
Source: https://github.com/intel/cve-bin-tool/actions/runs/7780736331
Is this also a network error or something worth looking at?
@terriko @anthonyharrison