CVE-2016-3461
First published: Thu Apr 21 2016(Updated: )
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.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MySQL Enterprise Monitor | =3.0.25 | |
| MySQL Enterprise Monitor | =3.1.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-3461?
CVE-2016-3461 has a high severity rating as it can lead to potential breaches in confidentiality, integrity, and availability.
How do I fix CVE-2016-3461?
To fix CVE-2016-3461, upgrade MySQL Enterprise Monitor to version 3.0.26 or 3.1.3 or later.
What components are affected by CVE-2016-3461?
CVE-2016-3461 affects the MySQL Enterprise Monitor component in Oracle MySQL versions 3.0.25 and earlier, and 3.1.2 and earlier.
Can CVE-2016-3461 be exploited remotely?
Yes, CVE-2016-3461 can be exploited by remote administrators through specific vectors related to monitoring the server.
What are the potential impacts of CVE-2016-3461?
The potential impacts of CVE-2016-3461 include unauthorized access and disruption of service due to its effects on confidentiality, integrity, and availability.
- agent/type
- agent/severity
- agent/author
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- 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.0.25
- version/mysql enterprise monitor/3.1.2