CVE-2016-3461
CVE-2016-3461 is a high-severity vulnerability in Oracle Mysql Enterprise Monitor with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: High (CVSS 3.x base score 7.2)
- CVSS v2: 4.3
- EPSS exploit prediction: 2% (74th percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Oracle Mysql Enterprise Monitor
- Published:
- Last modified:
Description
Unspecified vulnerability in the MySQL Enterprise Monitor component in Oracle MySQL 3.0.25 and earlier and 3.1.2 and earlier allows remote administrators to affect confidentiality, integrity, and availability via vectors related to Monitoring: Server.
Frequently asked questions
- What is CVE-2016-3461?
- Unspecified vulnerability in the MySQL Enterprise Monitor component in Oracle MySQL 3.0.25 and earlier and 3.1.2 and earlier allows remote administrators to affect confidentiality, integrity, and availability via vectors related to Monitoring: Server.
- How severe is CVE-2016-3461?
- CVE-2016-3461 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2016-3461 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (74th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2016-3461?
- CVE-2016-3461 primarily affects Oracle Mysql Enterprise Monitor. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2016-3461?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2016-3461 published?
- CVE-2016-3461 was published on 2016-04-21 and last updated on 2026-06-17.
References
- http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html
- http://www.securitytracker.com/id/1035606
- https://www.tenable.com/security/research/tra-2016-11
Affected products (2)
- cpe:2.3:a:oracle:mysql_enterprise_monitor:3.0.25:*:*:*:*:*:*:*
- cpe:2.3:a:oracle:mysql_enterprise_monitor:3.1.2:*:*:*:*:*:*:*
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…