Open loosebazooka opened 7 months ago
Hi @loosebazooka ! Thanks for the issue; I'm sorry for my late reply, and that you're having issue building the fuzzer for fuzzing protobuz for sigstore-java. A quick search shows you're using JUnit 5, so that is good. I'm not super proficient on oss-fuzz. But you can try again with Jazzer?
Sorry I know that was a lot of info, I'm working on a reproducer right now, trying to get something minimal. These tests don't use junit5. They follow the process outlined in the ozzfuzz docs for jazzer (https://google.github.io/oss-fuzz/getting-started/new-project-guide/jvm-lang/)
So maybe I don't understand what's going on with the oss_fuzz build, but it appears to be a 2-step process where there's a build
phase and a run
phase.
The build
phase in this case appears to be executing fuzzers though? Anyway, this appears to be a genuine issue discovered by fuzzing just at weird "build" phase of the fuzzing process (on oss_fuzz). Any idea who would be the right person to direct this to?
Yeah, that's a tough one. I'm really not the expert on oss-fuzz and jazzer for this situation. It seems like this is urgent or a task that you need to finish quickly. Is that an accurate assumption? In which case, can you email me at david.merian@code-intelligence.com ?
It's not super urgent. But I can still email you if it makes sense
Yeah let's move it to email so I can get the whole picture.
Thank you!
I'm not sure exactly how to debug this as I'm not sure where the issue is occuring? Is it during instrumentation? My knowledge of the inner workings of the fuzzing process are weak at best.
Errors are from oss-fuzz, I can add more details, but I'm not sure what's useful.
Full log might be public here: https://github.com/sigstore/sigstore-java/actions/runs/8577430969/job/23510004362?pr=674
The snippet in question. This happened when I updated protobuf generators from v3.x to v4.x. I can't even tell if this is useful for debugging
I tried not instrumenting the protobuf libraries, but that seemed to not help.