An issue was discovered in WavPack 5.1.0 and earlier for W64 input. Out-of-bounds writes can occur because ParseWave64HeaderConfig in wave64.c does not validate the sizes of unknown chunks before attempting memory allocation, related to a lack of integer-overflow protection within a bytes_to_copy calculation and subsequent malloc call, leading to insufficient memory allocation.
Created mingw-wavpack tracking bugs for this issue:
Affects: epel-7 [bug 1574720]
Affects: fedora-all [bug 1574723]
Created wavpack tracking bugs for this issue:
Affects: fedora-all [bug 1574721]
Wave64 support was added in WavPack 4.80+
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):