WavPack 5.1.0 and earlier is affected by: CWE-457: Use of Uninitialized Variable. The impact is: Unexpected control flow, crashes, and segfaults. The component is: ParseWave64HeaderConfig (wave64.c:211). The attack vector is:Maliciously crafted .wav file. Upstream Issue: https://github.com/dbry/WavPack/issues/68 Upstream Patch: https://github.com/dbry/WavPack/commit/33a0025d1d63ccd05d9dbaa6923d52b1446a62fe
Created mingw-wavpack tracking bugs for this issue: Affects: epel-7 [bug 1737741] Affects: fedora-all [bug 1737743] Created wavpack tracking bugs for this issue: Affects: fedora-all [bug 1737742]
Statement: This issue affects the versions of wavpack as shipped with Red Hat Enterprise Linux 8. This flaw has been classified as 'Low' regarding the security impact by the Red Hat Product Security Team. Red Hat Enterprise Linux versions prior than the mentioned before are not affected as wavpack shipped with those versions doesn't support the file format required.
wavpack application doesn't properly initialize the WaveHeader data structure. When parsing Wave64 file's header without the number of channels information it eventually lead to a 'Division by zero' exception causing DoS. This has a low impact as only the single run from a single user opening the crafted file will be affected.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:1581 https://access.redhat.com/errata/RHSA-2020:1581
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-1010319