What is the severity of CVE-2017-3307?

CVE-2017-3307 has been classified as difficult to exploit, but it poses a potential risk if exploited by a high privileged attacker.

How do I fix CVE-2017-3307?

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

What are the affected versions for CVE-2017-3307?

The affected versions for CVE-2017-3307 include MySQL Enterprise Monitor 3.1.6.8003 and earlier, 3.2.1182 and earlier, and 3.3.2.1162 and earlier.

Who is impacted by CVE-2017-3307?

CVE-2017-3307 impacts organizations using affected versions of MySQL Enterprise Monitor, particularly those with high privileged accounts.

Is CVE-2017-3307 related to any specific components?

CVE-2017-3307 specifically affects the Monitoring: Server component of Oracle MySQL's Enterprise Monitor.

Vulnerability/
CVE-2017-3307

low

3.6

24/4/2017

7/10/2024

CVE-2017-3307

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. Difficult to exploit 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. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of 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 3.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/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-3307?
CVE-2017-3307 has been classified as difficult to exploit, but it poses a potential risk if exploited by a high privileged attacker.
How do I fix CVE-2017-3307?
To fix CVE-2017-3307, upgrade your MySQL Enterprise Monitor to version 3.1.6.8004 or later, 3.2.1183 or later, or 3.3.2.1163 or later.
What are the affected versions for CVE-2017-3307?
The affected versions for CVE-2017-3307 include MySQL Enterprise Monitor 3.1.6.8003 and earlier, 3.2.1182 and earlier, and 3.3.2.1162 and earlier.
Who is impacted by CVE-2017-3307?
CVE-2017-3307 impacts organizations using affected versions of MySQL Enterprise Monitor, particularly those with high privileged accounts.
Is CVE-2017-3307 related to any specific components?
CVE-2017-3307 specifically affects the Monitoring: Server component of Oracle MySQL's 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