First published: Sun Apr 29 2018(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/wavpack | 5.4.0-1 5.6.0-1 5.7.0-1 | |
ubuntu/wavpack | <5.1.0-2ubuntu0.3 | 5.1.0-2ubuntu0.3 |
ubuntu/wavpack | <5.1.0-2ubuntu1.1 | 5.1.0-2ubuntu1.1 |
libwavpack1 | <=5.1.0 | |
Debian | =8.0 | |
Debian | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-10538 is classified as a high severity vulnerability due to the potential for out-of-bounds writes and memory corruption.
To mitigate CVE-2018-10538, upgrade WavPack to version 5.4.0-1 or higher for Debian systems, or 5.1.0-2ubuntu0.3 for affected Ubuntu versions.
CVE-2018-10538 affects WavPack versions 5.1.0 and earlier across multiple distributions including Debian and Ubuntu.
Exploitation of CVE-2018-10538 can lead to application crashes and potential arbitrary code execution due to memory corruption.
Yes, CVE-2018-10538 specifically affects WAV input processed by the WavPack audio compression library.