Bug 1274780 (CVE-2015-4866)

Summary:	CVE-2015-4866 mysql: unspecified vulnerability related to Server:InnoDB (CPU October 2015)
Product:	[Other] Security Response	Reporter:	Martin Prpič <mprpic>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	abaron, aortega, apevec, ayoung, chrisw, dallan, databases-maint, dciabrin, gkotton, hhorak, jdornak, jorton, jschluet, jstanek, lhh, lpeer, markmc, mbayer, mmaslano, mmuzila, rbryant, rohara, sclewis, tdecacqu, yeylon
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	mysql 5.6.24, mariadb 10.1.8, mariadb 10.0.18	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-29 07:26:00 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:	1276223
Bug Blocks:	1274745

Description Martin Prpič 2015-10-23 14:01:04 UTC

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server : InnoDB). Supported versions that are affected are 5.6.23 and earlier. Easily exploitable vulnerability allows successful authenticated network attacks via multiple protocols. Successful attack of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.

External References:

http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL

Comment 1 Huzaifa S. Sidhpurwala 2015-10-29 07:05:31 UTC

Created community-mysql tracking bugs for this issue:

Affects: fedora-all [bug 1276223]

Comment 3 Tomas Hoger 2016-01-25 22:33:55 UTC

Oracle CPU indicates this issue was fixed in MySQL 5.6.24.  That is the first MySQL 5.6 version that was added to Red Hat Software Collections rh-mysql56 collection and hence the product was never affected by this issue.

MariaDB upstream indicates this issue was fixed in version 10.0.18:

https://mariadb.com/kb/en/mariadb/mariadb-10018-release-notes/

and hence this problem was corrected in the rh-mariadb100 collection in Red Hat Software Collections via the following erratum:

https://rhn.redhat.com/errata/RHSA-2015-1646.html