Bug 1499959 (CVE-2017-14633)

Summary:	CVE-2017-14633 libvorbis: Out-of-bounds array read in the function mapping0_forward()
Product:	[Other] Security Response	Reporter:	Andrej Nemec <anemec>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ajax, alexl, caillon+fedoraproject, dkholia, erik-fedora, gnome-sig, hdegoede, klember, rhughes, rstrode, sandmann, tuxator
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	An out-of-bounds read flaw was found in the way libvorbis handled processing of Ogg Vorbis format files. This flaw could potentially be used to crash an application using libvorbis by tricking the application into processing specially crafted files.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-21 10:03:53 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:	1480648, 1480649, 1480650
Bug Blocks:	1499962

Description Andrej Nemec 2017-10-09 15:31:49 UTC

An out-of-bounds array read vulnerability exists in libvorbis in the function mapping0_forward() in mapping0.c, which may lead to DoS when operating on a crafted audio file with vorbis_analysis().

Upstream issue:

https://gitlab.xiph.org/xiph/vorbis/issues/2329

Upstream patches:

https://github.com/xiph/vorbis/commit/a79ec216cd1190
https://github.com/xiph/vorbis/commit/c1c2831fc7306d

Comment 1 Andrej Nemec 2017-10-09 15:35:47 UTC

Created libvorbis tracking bugs for this issue:

Affects: fedora-all [bug 1480650]


Created mingw-libvorbis tracking bugs for this issue:

Affects: epel-7 [bug 1480649]
Affects: fedora-all [bug 1480648]

Comment 4 Dhiru Kholia 2017-12-21 10:03:01 UTC

Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.