How severe is CVE-2017-3307?

CVE-2017-3307 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and user interaction. Impact on confidentiality is none, integrity low, and availability low.

Is CVE-2017-3307 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (62nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-3307?

CVE-2017-3307 affects Oracle Mysql Enterprise Monitor. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-3307?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-3307 published?

CVE-2017-3307 was published on 2017-04-24 and last updated on 2026-06-17.

CVE-2017-3307

CVE-2017-3307 is a low-severity vulnerability in Oracle Mysql Enterprise Monitor with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 3.x base score 3.1)
CVSS v2: 3.6
EPSS exploit prediction: 1% (62nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Mysql Enterprise Monitor
Published: 2017-04-24
Last modified: 2026-06-17

Description

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).

Frequently asked questions

What is CVE-2017-3307?: 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).
How severe is CVE-2017-3307?: CVE-2017-3307 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and user interaction. Impact on confidentiality is none, integrity low, and availability low.
Is CVE-2017-3307 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (62nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-3307?: CVE-2017-3307 affects Oracle Mysql Enterprise Monitor. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-3307?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-3307 published?: CVE-2017-3307 was published on 2017-04-24 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:oracle:mysql_enterprise_monitor:*:*:*:*:*:*:*:*

More vulnerabilities in Oracle Mysql Enterprise Monitor

CVE-2013-4316 — Critical (CVSS 10.0): Apache Struts 2.0.0 through 2.3.15.1 enables Dynamic Method Invocation by default, which has unknown impact and attack…
CVE-2022-22965 — Critical (CVSS 9.8): A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data…
CVE-2022-22963 — Critical (CVSS 9.8): In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is…
CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
CVE-2021-3711 — Critical (CVSS 9.8): In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt().…
CVE-2020-17530 — Critical (CVSS 9.8): Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution. Affected…

All CVEs affecting Oracle Mysql Enterprise Monitor →