Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1640317 - (CVE-2018-3247) CVE-2018-3247 mysql: Server: Merge unspecified vulnerability (CPU Oct 2018)
CVE-2018-3247 mysql: Server: Merge unspecified vulnerability (CPU Oct 2018)
Status: NEW
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=20181016,repor...
: Security
Depends On: 1640559 1642059 1642068 1642165 1643049
Blocks: 1640349
  Show dependency treegraph
 
Reported: 2018-10-17 16:27 EDT by Tomas Hoger
Modified: 2018-10-25 08:27 EDT (History)
24 users (show)

See Also:
Fixed In Version: mysql 5.6.42, mysql 5.7.24, mysql 8.0.13
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Tomas Hoger 2018-10-17 16:27:32 EDT
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Merge). Supported versions that are affected are 5.6.41 and prior, 5.7.23 and prior and  8.0.12 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data.

External References:

http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
Comment 1 Tomas Hoger 2018-10-18 06:24:01 EDT
Created community-mysql tracking bugs for this issue:

Affects: fedora-all [bug 1640559]

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