Bug 1574728 (CVE-2018-10538)

Summary:	CVE-2018-10538 wavpack: out of bounds write in ParseRiffHeaderConfig in riff.c
Product:	[Other] Security Response	Reporter:	Laura Pardo <lpardo>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	lemenkov, mlichvar, valtri
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-21 20:02:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1574720, 1574721, 1574723, 1574732, 1609113
Bug Blocks:	1574733

Description Laura Pardo 2018-05-03 21:45:22 UTC

An issue was discovered in WavPack 5.1.0 and earlier for WAV input. Out-of-bounds writes can occur because ParseRiffHeaderConfig in riff.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 21:50:55 UTC

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-27 03:09:15 UTC

The affected chunk of code in wavpack prior to 4.80 is in cli/wavpack.c

Comment 4 Doran Moppert 2018-07-27 03:20:34 UTC

Statement:

Red Hat Enterprise Linux 6 is now in Maintenance support 2 Phase of the support and maintenance life cycle. This issue has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/