Bug 1276265 (CVE-2015-4730) - CVE-2015-4730 mysql: unspecified vulnerability related to Server:Types (CPU October 2015)
Summary: CVE-2015-4730 mysql: unspecified vulnerability related to Server:Types (CPU O...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2015-4730
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: 1276223 1276224 1276225
Blocks: 1274745
TreeView+ depends on / blocked
 
Reported: 2015-10-29 10:01 UTC by Martin Prpič
Modified: 2021-02-17 04:46 UTC (History)
25 users (show)

Fixed In Version: mysql 5.6.21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-29 10:05:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Martin Prpič 2015-10-29 10:01:26 UTC 
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server : Types). Supported versions that are affected are 5.6.20 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 Martin Prpič 2015-10-29 10:02:20 UTC 
Created mariadb tracking bugs for this issue:

Affects: fedora-all [bug 1276224]
Comment 2 Martin Prpič 2015-10-29 10:02:33 UTC 
Created community-mysql tracking bugs for this issue:

Affects: fedora-all [bug 1276223]
Comment 3 Martin Prpič 2015-10-29 10:02:45 UTC 
Created mariadb-galera tracking bugs for this issue:

Affects: fedora-all [bug 1276225]
Comment 5 Tomas Hoger 2016-01-26 11:45:49 UTC 
Oracle CPU indicates this issue was fixed in MySQL 5.6.21.  The first MySQL 5.6 version that was added to Red Hat Software Collections rh-mysql56 collection was 5.6.24 and hence the product was never affected by this issue.
Note You need to log in before you can comment on or make changes to this bug.