Bug 1609193 (CVE-2018-1000223) - CVE-2018-1000223 soundtouch: Heap-based buffer overflow in SoundStretch/WavFile.cpp:WavInFile::readHeaderBlock() potentially leading to code execution
Summary: CVE-2018-1000223 soundtouch: Heap-based buffer overflow in SoundStretch/WavFi...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-1000223
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1609194 1609195 Engineering1609196 Engineering1609754
Blocks: Embargoed1601622
TreeView+ depends on / blocked
 
Reported: 2018-07-27 09:12 UTC by Adam Mariš
Modified: 2021-10-25 09:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
SoundStretch command-line utility packaged with SoundTouch library is vulnerable to heap-based buffer overflow in WavFile.cpp:WavInFile::readHeaderBlock() function that can lead to arbitrary code execution when processing untrusted file input.
Clone Of:
Environment:
Last Closed: 2021-10-25 09:49:06 UTC

Attachments (Terms of Use)

Description Adam Mariš 2018-07-27 09:12:42 UTC 
WavInFile::readHeaderBlock() function in SoundStretch/WavFile.cpp is vulnerable to heap buffer overflow that can lead to arbitrary code execution when processing malicious file. This issue does affect only SoundStretch utility, not SoundTouch library.

Upstream issue:

https://gitlab.com/soundtouch/soundtouch/issues/6
Comment 1 Adam Mariš 2018-07-27 09:13:13 UTC 
Created soundtouch tracking bugs for this issue:

Affects: epel-6 [bug 1609195]
Affects: fedora-all [bug 1609194]
Comment 4 Adam Mariš 2018-08-14 12:57:27 UTC 
Upstream fix:

https://gitlab.com/soundtouch/soundtouch/commit/9e02d9b04fda6c1f44336ff00bb5af1e2ffc039e
https://gitlab.com/soundtouch/soundtouch/commit/e0240689056e4182fffdc2a16aa6e3425a15e275
https://gitlab.com/soundtouch/soundtouch/commit/46531e5b92dd80dd9a7947463d6224fc7cb21967
Note You need to log in before you can comment on or make changes to this bug.