Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1444407 - (CVE-2017-3589) CVE-2017-3589 mysql-connector-java: Connector/J unspecified vulnerability (CPU Apr 2017)
CVE-2017-3589 mysql-connector-java: Connector/J unspecified vulnerability (CP...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170419,reported=2...
: Security
Depends On: 1444418 1464466 1464467
Blocks: 1444415
  Show dependency treegraph
 
Reported: 2017-04-21 05:55 EDT by Adam Mariš
Modified: 2018-06-29 18:20 EDT (History)
34 users (show)

See Also:
Fixed In Version:
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 Adam Mariš 2017-04-21 05:55:37 EDT
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.41 and earlier. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data. 

External References:

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMySQL
Comment 1 Adam Mariš 2017-04-21 06:03:13 EDT
Created mysql-connector-java tracking bugs for this issue:

Affects: fedora-all [bug 1444418]
Comment 11 Stefan Cornelius 2018-02-22 04:51:02 EST
Statement:

This issue affects the versions of mysql-connector-java as shipped with Red Hat Enterprise Linux 6 and 7.

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