Sorry for the confusion, maybe I didn't explain it clearly. As an secrurity researcher, I'm trying to develop a fuzzer and find those crafted expectational cases to validate the fuzzers' efficiency and if possible, help developers to fix those bugs (if they're considered as bugs). Are they specificaly crafted, with bogus sample rate and number of channels etc to trigger these exceptional cases you're correct, it's not a valid aiff files. since the goal of fuzzer is finding crafted file to trigger...
What is the @@ in 'sox --single-threaded @@ -t aiff /dev/null' supposed to be? you're correct, @@ is the place to put the input file. This is fuzzer's argument format. And whatever audio file I give there, it works. did you try the file given in poc.zip? in my environment I can reproduce these two bugs via the poc file given in zip.
If you have time to do so, thanks a lot!
Fix Credit: Han Zheng(NCNIPC of China, Hexhive) Yin Li, Xiaotong Jiao (NCNIPC of China)
Fix Credit: Han Zheng(NCNIPC of China, Hexhive) Yin Li, Xiaotong Jiao (NCNIPC of China)
Fix Credit: Han Zheng(NCNIPC of China, Hexhive) Yin Li, Xiaotong Jiao (NCNIPC of China)
Thanks for the quick fix & commit, in my test environment both #145 and #148 are fixed.
[BUG] two null pointers dereference in put_patternarc, genpict2e.c:2395 and 2400, diffferent from #145