What is the severity of CVE-2017-3306?

CVE-2017-3306 is considered a high severity vulnerability due to its easily exploitable nature allowing high privileged attackers to gain unauthorized access.

How do I fix CVE-2017-3306?

To fix CVE-2017-3306, upgrade to MySQL Enterprise Monitor version 3.1.6.8004, 3.2.1183, or 3.3.2.1163, or later versions.

Which versions are affected by CVE-2017-3306?

CVE-2017-3306 affects MySQL Enterprise Monitor versions 3.1.6.8003 and earlier, 3.2.1182 and earlier, and 3.3.2.1162 and earlier.

What components of Oracle MySQL are impacted by CVE-2017-3306?

CVE-2017-3306 impacts the MySQL Enterprise Monitor component, specifically the monitoring server subcomponent.

Who may exploit CVE-2017-3306?

CVE-2017-3306 can be exploited by high privileged attackers with network access to the MySQL Enterprise Monitor.

Vulnerability/
CVE-2017-3306

high

8.3

24/4/2017

7/10/2024

CVE-2017-3306

First published: Mon Apr 24 2017(Updated: )

Vulnerability in the MySQL Enterprise Monitor component of Oracle MySQL (subcomponent: Monitoring: Server). Supported versions that are affected are 3.1.6.8003 and earlier, 3.2.1182 and earlier and 3.3.2.1162 and earlier. Easily "exploitable" vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Enterprise Monitor. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Enterprise Monitor, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Enterprise Monitor accessible data as well as unauthorized access to critical data or complete access to all MySQL Enterprise Monitor accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Enterprise Monitor. CVSS 3.0 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL Enterprise Monitor	>=3.1.0<=3.1.6.8003
MySQL Enterprise Monitor	>=3.2.0<=3.2.1182
MySQL Enterprise Monitor	>=3.3.0<=3.3.2.1162

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-3306?
CVE-2017-3306 is considered a high severity vulnerability due to its easily exploitable nature allowing high privileged attackers to gain unauthorized access.
How do I fix CVE-2017-3306?
To fix CVE-2017-3306, upgrade to MySQL Enterprise Monitor version 3.1.6.8004, 3.2.1183, or 3.3.2.1163, or later versions.
Which versions are affected by CVE-2017-3306?
CVE-2017-3306 affects MySQL Enterprise Monitor versions 3.1.6.8003 and earlier, 3.2.1182 and earlier, and 3.3.2.1162 and earlier.
What components of Oracle MySQL are impacted by CVE-2017-3306?
CVE-2017-3306 impacts the MySQL Enterprise Monitor component, specifically the monitoring server subcomponent.
Who may exploit CVE-2017-3306?
CVE-2017-3306 can be exploited by high privileged attackers with network access to the MySQL Enterprise Monitor.

agent/type
agent/severity
agent/remedy
agent/author
agent/references
agent/description
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/oracle
canonical/mysql enterprise monitor
version/mysql enterprise monitor/3.1.0
version/mysql enterprise monitor/3.1.6.8003
version/mysql enterprise monitor/3.2.0
version/mysql enterprise monitor/3.2.1182
version/mysql enterprise monitor/3.3.0
version/mysql enterprise monitor/3.3.2.1162