An issue was discovered in WavPack 5.1.0 and earlier for WAV input. Out-of-bounds writes can occur because ParseRiffHeaderConfig in riff.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. References: https://github.com/dbry/WavPack/issues/33 Patch: https://github.com/dbry/WavPack/commit/6f8bb34c2993a48ab9afbe353e6d0cff7c8d821d
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]
The affected chunk of code in wavpack prior to 4.80 is in cli/wavpack.c
Statement: Red Hat Enterprise Linux 6 is now in Maintenance support 2 Phase of the support and maintenance life cycle. This issue has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/