Bug 1666861 (CVE-2019-2435) - CVE-2019-2435 mysql-connector-python: unauthorized access to data
Summary: CVE-2019-2435 mysql-connector-python: unauthorized access to data
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-2435
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1666862 1666863
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-16 19:14 UTC by Laura Pardo
Modified: 2020-04-24 15:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:45:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Laura Pardo 2019-01-16 19:14:00 UTC
A flaw was found in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/Python). Supported versions that are affected are 8.0.13 and prior and 2.1.8 and prior. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. This vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Connectors accessible data as well as unauthorized access to critical data or complete access to all MySQL Connectors accessible data.


References:
http://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#CVE-2019-2435

Comment 1 Laura Pardo 2019-01-16 19:14:30 UTC
Created mysql-connector-python tracking bugs for this issue:

Affects: epel-all [bug 1666862]
Affects: fedora-all [bug 1666863]

Comment 2 Product Security DevOps Team 2019-06-10 10:45:53 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


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