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.
The product writes data past the end, or before the beginning, of the intended buffer.
| Link | Tags |
|---|---|
| https://github.com/dbry/WavPack/issues/33 | issue tracking exploit third party advisory |
| https://www.debian.org/security/2018/dsa-4197 | third party advisory vendor advisory |
| https://usn.ubuntu.com/3637-1/ | third party advisory vendor advisory |
| https://github.com/dbry/WavPack/commit/6f8bb34c2993a48ab9afbe353e6d0cff7c8d821d | third party advisory patch |
| https://seclists.org/bugtraq/2019/Dec/37 | mailing list |
| http://packetstormsecurity.com/files/155743/Slackware-Security-Advisory-wavpack-Updates.html | |
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6CFFFWIWALGQPKINRDW3PRGRD5LOLGZA/ | vendor advisory |
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BRWQNE3TH5UF64IKHKKHVCHJHUOVKJUH/ | vendor advisory |