What is the severity of CVE-2016-5590?

CVE-2016-5590 is considered to be an easily exploitable vulnerability that affects MySQL Enterprise Monitor.

How do I fix CVE-2016-5590?

To fix CVE-2016-5590, it is recommended to upgrade MySQL Enterprise Monitor to version 3.1.3.7857 or later.

Who is affected by CVE-2016-5590?

CVE-2016-5590 affects users of MySQL Enterprise Monitor versions 3.1.3.7856 and earlier.

What type of vulnerability is CVE-2016-5590?

CVE-2016-5590 is a vulnerability in the Monitoring Agent component of MySQL Enterprise Monitor.

Can CVE-2016-5590 be exploited remotely?

Yes, CVE-2016-5590 can be exploited by a high privileged attacker with network access via TLS.

Vulnerability/
CVE-2016-5590

high

7.2

27/1/2017

9/10/2024

CVE-2016-5590

First published: Fri Jan 27 2017(Updated: )

Vulnerability in the MySQL Enterprise Monitor component of Oracle MySQL (subcomponent: Monitoring: Agent). Supported versions that are affected are 3.1.3.7856 and earlier. Easily exploitable vulnerability allows high privileged attacker with network access via TLS to compromise MySQL Enterprise Monitor. Successful attacks of this vulnerability can result in takeover of MySQL Enterprise Monitor. CVSS v3.0 Base Score 7.2 (Confidentiality, Integrity and Availability impacts).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL Enterprise Monitor	<=3.1.3.7856

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-5590?
CVE-2016-5590 is considered to be an easily exploitable vulnerability that affects MySQL Enterprise Monitor.
How do I fix CVE-2016-5590?
To fix CVE-2016-5590, it is recommended to upgrade MySQL Enterprise Monitor to version 3.1.3.7857 or later.
Who is affected by CVE-2016-5590?
CVE-2016-5590 affects users of MySQL Enterprise Monitor versions 3.1.3.7856 and earlier.
What type of vulnerability is CVE-2016-5590?
CVE-2016-5590 is a vulnerability in the Monitoring Agent component of MySQL Enterprise Monitor.
Can CVE-2016-5590 be exploited remotely?
Yes, CVE-2016-5590 can be exploited by a high privileged attacker with network access via TLS.

agent/type
agent/severity
agent/remedy
agent/author
agent/references
agent/description
agent/event
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/last-modified-date
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.1.3.7856

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-5590?
CVE-2016-5590 is considered to be an easily exploitable vulnerability that affects MySQL Enterprise Monitor.
How do I fix CVE-2016-5590?
To fix CVE-2016-5590, it is recommended to upgrade MySQL Enterprise Monitor to version 3.1.3.7857 or later.
Who is affected by CVE-2016-5590?
CVE-2016-5590 affects users of MySQL Enterprise Monitor versions 3.1.3.7856 and earlier.
What type of vulnerability is CVE-2016-5590?
CVE-2016-5590 is a vulnerability in the Monitoring Agent component of MySQL Enterprise Monitor.
Can CVE-2016-5590 be exploited remotely?
Yes, CVE-2016-5590 can be exploited by a high privileged attacker with network access via TLS.