Bug 867518 - (CVE-2012-3147) CVE-2012-3147 mysql: unspecified client vulnerability with integrity and availability impact
CVE-2012-3147 mysql: unspecified client vulnerability with integrity and avai...
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On:
Blocks: 867241 mysql-cpu-2012-10
  Show dependency treegraph
Reported: 2012-10-17 12:07 EDT by Jan Lieskovsky
Modified: 2012-10-26 10:29 EDT (History)
5 users (show)

See Also:
Fixed In Version: mysql 5.5.27
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-26 09:08:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2012-10-17 12:07:08 EDT
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.5.26 and earlier, allows remote unauthenticated users to affect integrity and availability via unknown vectors related to MySQL client.

[1] http://www.oracle.com/technetwork/topics/security/cpuoct2012-1515893.html
Comment 1 Tomas Hoger 2012-10-26 09:08:59 EDT
Text of the Oracle flaw description:

  Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent:
  MySQL Client). Supported versions that are affected are 5.5.26 and earlier.
  Easily exploitable vulnerability allows successful unauthenticated network
  attacks via multiple protocols. Successful attack of this vulnerability can
  result in unauthorized update, insert or delete access to some MySQL Server
  accessible data and ability to cause a partial denial of service (partial DOS)
  of MySQL Server.


Upstream notes this issue only affected MySQL versions 5.5.  Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected.  Current Fedora versions are already updated to fixed upstream version.  Closing.

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