Closed blu3sh0rk closed 1 year ago
Hi, and thanks for reporting this!
The problem was that the seektest
expects a valid WavPack file, not the output of a fuzzer. It's purpose is to test the seeking function of libwavpack
with varying, but valid, files. In this case the WavPack file was corrupt and did not decode correctly, and the manner in which it failed was not being checked for. I have pushed a fix for this including that check, but there could certainly be other bugs in the tester, not to mention memory leaks.
Since wvtest
is not a user-facing program, nor even available in any distribution or package, I do not consider this a security issue. And I also believe that even if a bug was found in the libwavpack
seeking code, it would not be a great security risk either because of the difficulty of triggering it outside of the lab.
I would be very curious as to how you think this issue might be exploited to cause a DoS or RCE. :smile:
Desctiption
A heap-buffer-overflow has occurred when running program wvtest in function MD5_Final at WavPack/cli/md5.c:283:2
Version
Steps to reproduce
POC
https://github.com/blu3sh0rk/Fuzzing-crash/blob/main/wvtest/POC1
Code at WavPack/cli/md5.c:283:2
Environment:
IMPACT
Potentially causing DoS and RCE