LiveActive security incident?Get immediate response
CVE Record

CVE-2016-5590: Vulnerability in the MySQL Enterprise Monitor component of Oracle MySQL (subcomponent: Monitoring: Agent).

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-5590 affects Oracle MySQL Enterprise Monitor, specifically the Monitoring Agent. If an already high-privileged attacker can reach it over TLS, Oracle says the issue can allow takeover of MySQL Enterprise Monitor. This is not a broad unauthenticated internet-style flaw, but it matters where monitoring infrastructure is reachable by powerful internal or administrative accounts. Exposure is likely limited to organizations running MySQL Enterprise Monitor 3.1.3.7856 or earlier, especially where the Monitoring Agent is reachable over TLS by administrative users or service accounts. The bundle does not identify affected operating systems, deployment patterns, or cloud services. Treat as a high-priority legacy Oracle/MySQL remediation item if MySQL Enterprise Monitor is in use. Business urgency is highest where monitoring systems are reachable by many administrators or service accounts, because successful compromise could give control over the monitoring platform. Mitigation focus: Inventory MySQL Enterprise Monitor deployments and identify Monitoring Agent versions.; Prioritize systems running version 3.1.3.7856 or earlier.; Review Oracle January 2017 CPU guidance for the applicable fix or upgrade path..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-5590 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OracleMySQL Enterprise Monitor3.1.3.7856 and earlierListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.