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 1088208 - (CVE-2014-2444) CVE-2014-2444 mysql: unspecified vulnerability related to InnoDB (CPU April 2014)
CVE-2014-2444 mysql: unspecified vulnerability related to InnoDB (CPU April 2...
Status: CLOSED NOTABUG
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=20140415,repor...
: Security
Depends On: 1088237
Blocks: 1088219
  Show dependency treegraph
 
Reported: 2014-04-16 05:00 EDT by Huzaifa S. Sidhpurwala
Modified: 2014-07-16 14:40 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-02 06:17:30 EDT
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 Huzaifa S. Sidhpurwala 2014-04-16 05:00:42 EDT
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: InnoDB). Supported versions that are affected are 5.6.15 and earlier. Easily exploitable vulnerability allows successful authenticated network attacks via multiple protocols. Successful attack of this vulnerability can result in unauthorized takeover of MySQL Server possibly including arbitrary code execution within the MySQL Server. 

External References:

http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL
Comment 1 Huzaifa S. Sidhpurwala 2014-04-16 05:52:12 EDT
Created community-mysql tracking bugs for this issue:

Affects: fedora-rawhide [bug 1088237]
Comment 3 Vincent Danen 2014-07-16 14:40:02 EDT
Statement:

Not vulnerable.  This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product.

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