First published: Thu Jul 11 2019(Updated: )
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. The fixed version is: After commit https://github.com/dbry/WavPack/commit/33a0025d1d63ccd05d9dbaa6923d52b1446a62fe.
Credit: josh@bress.net
Affected Software | Affected Version | How to fix |
---|---|---|
ubuntu/wavpack | <5.1.0-2ubuntu1.4 | 5.1.0-2ubuntu1.4 |
ubuntu/wavpack | <5.1.0-5ubuntu0.2 | 5.1.0-5ubuntu0.2 |
debian/wavpack | 5.4.0-1 5.6.0-1 5.7.0-1 | |
libwavpack1 | <=5.1.0 | |
Fedora | =29 | |
Fedora | =30 | |
Fedora | =31 | |
Ubuntu | =18.04 | |
Ubuntu | =19.04 | |
Debian | =9.0 | |
Wavpack | <=5.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-1010319 has a moderate severity due to potential crashes and unexpected control flow.
To fix CVE-2019-1010319, update WavPack to version 5.1.0-2ubuntu1.4 or later for Ubuntu and to version 5.4.0-1 or later for Debian.
The impact of CVE-2019-1010319 includes the potential for application crashes and segmentation faults when processing maliciously crafted .wav files.
Versions of WavPack up to and including 5.1.0 are affected by CVE-2019-1010319.
Yes, CVE-2019-1010319 can be exploited remotely through the use of maliciously crafted .wav files.