First published: Sun Apr 29 2018(Updated: )
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.
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-10540 is classified as a high severity vulnerability due to potential exploitation through out-of-bounds writes.
To fix CVE-2018-10540, update WavPack to version 5.4.0-1 or later if using Debian, or 5.1.0-2ubuntu0.3 or later for Ubuntu.
CVE-2018-10540 affects WavPack version 5.1.0 and earlier on Debian and Ubuntu operating systems.
CVE-2018-10540 involves a lack of validation for the sizes of unknown chunks, leading to possible out-of-bounds memory writes.
Yes, CVE-2018-10540 can potentially be exploited remotely if an attacker can feed specially crafted data to WavPack.