CVE-2017-3307
Last modified
CVE-2017-3307 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.10% chance of exploitation in the next 30 days.
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).
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oracle | Mysql Enterprise Monitor | >= 3.1.0, <= 3.1.6.8003 |
| Oracle | Mysql Enterprise Monitor | >= 3.2.0, <= 3.2.1182 |
| Oracle | Mysql Enterprise Monitor | >= 3.3.0, <= 3.3.2.1162 |
References
- http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/97844Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038287Third Party Advisory, VDB Entry
- http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/97844Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038287Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3307?
How severe is CVE-2017-3307?
How do I fix CVE-2017-3307?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-3301Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3302Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and…
- CVE-2017-3303Vulnerability in the Oracle XML Gateway component of Oracle …
- CVE-2017-3304Vulnerability in the MySQL Cluster component of Oracle MySQL…
- CVE-2017-3305Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3306Vulnerability in the MySQL Enterprise Monitor component of O…
- CVE-2017-3308Vulnerability in the MySQL Server component of Oracle MySQL …7.7
- CVE-2017-3309Vulnerability in the MySQL Server component of Oracle MySQL …7.7
- CVE-2017-3310Vulnerability in the OJVM component of Oracle Database Serve…
- CVE-2017-3311Vulnerability in the Application Testing Suite component of …
- CVE-2017-3312Vulnerability in the MySQL Server component of Oracle MySQL …6.7
- CVE-2017-3313Vulnerability in the MySQL Server component of Oracle MySQL …4.7
Are you affected by CVE-2017-3307?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
