CVE-2017-3307
3.1 · LOWOverview
CVE-2017-3307 is a low-severity vulnerability affecting oracle mysql_enterprise_monitor. It was published on April 24, 2017 and has a CVSS 3.0 base score of 3.1 (LOW).
This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical 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).
Remediation
Check the references section for vendor advisories and patches from oracle. Update mysql_enterprise_monitor to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| oracle | mysql_enterprise_monitor | 3.1.0 | Affected |
References
Frequently Asked Questions
What is CVE-2017-3307?
CVE-2017-3307 is a low-severity vulnerability affecting oracle mysql_enterprise_monitor. It was published on April 24, 2017 and has a CVSS 3.0 base score of 3.1 (LOW).
How severe is CVE-2017-3307?
This vulnerability has a CVSS 3.0 base score of 3.1, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2017-3307?
Check the references section for vendor advisories and patches from oracle. Update mysql_enterprise_monitor to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2017-3307?
CyberStrike's AI-powered security agents can automatically detect CVE-2017-3307 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2017
View all →The BIOS in Intel Compute Stick systems based on 6th Gen Intel Core processors prior to version CC04
The BIOS in Intel NUC systems based on 6th Gen Intel Core processors prior to version KY0045 may all
The BIOS in Intel NUC systems based on 6th Gen Intel Core processors prior to version SY0059 may all
Xen PV guest before Xen 4.3 checked access permissions to MMIO ranges only after accessing them, all
Airwatch Inbox for Android contains a vulnerability that may allow a rooted device to decrypt the lo
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: InnoDB). Supporte
In BlackBerry QNX Software Development Platform (SDP) 6.6.0, an information disclosure vulnerability
In BlackBerry QNX Software Development Platform (SDP) 6.6.0 and 6.5.0 SP1 and earlier, an informatio
Dotclear before 2.10.3, when the Host header is not part of the web server routing process, allows r
A directory traversal exists in the handling of the MXIT protocol in Pidgin. Specially crafted MXIT
Clustered Data ONTAP versions 8.0, 8.3.1, and 8.3.2 contain a default privileged account which under
Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them