Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1574731 - (CVE-2018-10540) CVE-2018-10540 wavpack: out of bounds write in ParseWave64HeaderConfig in wave64.c
CVE-2018-10540 wavpack: out of bounds write in ParseWave64HeaderConfig in wav...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180422,repor...
: Security
Depends On: 1574720 1574723 1574732 1574721
Blocks: 1574733
  Show dependency treegraph
 
Reported: 2018-05-03 17:50 EDT by Laura Pardo
Modified: 2018-07-26 23:20 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Laura Pardo 2018-05-03 17:50:13 EDT
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.


References:
https://github.com/dbry/WavPack/issues/33

Patch:
https://github.com/dbry/WavPack/commit/6f8bb34c2993a48ab9afbe353e6d0cff7c8d821d
Comment 1 Laura Pardo 2018-05-03 17:51:43 EDT
Created mingw-wavpack tracking bugs for this issue:

Affects: epel-7 [bug 1574720]
Affects: fedora-all [bug 1574723]


Created wavpack tracking bugs for this issue:

Affects: fedora-all [bug 1574721]
Comment 3 Doran Moppert 2018-07-26 23:12:03 EDT
Wave64 support was added in WavPack 4.80+

Note You need to log in before you can comment on or make changes to this bug.