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: ParseCaffHeaderConfig (caff.c:486). The attack vector is: Maliciously crafted .wav file. The fixed version is: After commit https://github.com/dbry/WavPack/commit/f68a9555b548306c5b1ee45199ccdc4a16a6101b.
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-1010317 has a high severity due to the potential for unexpected control flow, crashes, and segmentation faults.
To fix CVE-2019-1010317, update WavPack to version 5.1.0-2ubuntu1.4 or later on Ubuntu, or to versions 5.4.0-1, 5.6.0-1, or 5.7.0-1 on Debian.
WavPack versions 5.1.0 and earlier are affected by CVE-2019-1010317.
CVE-2019-1010317 is caused by the use of uninitialized variables in the ParseCaffHeaderConfig function.
Users may experience crashes or unexpected behavior when processing maliciously crafted .wav files due to CVE-2019-1010317.