LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3123: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: libmysqld).

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: libmysqld). Supported versions that are affected are 5.6.42 and prior, 5.7.24 and prior and 8.0.13 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data. CVSS 3.0 Base Score 5.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-3123 is a MySQL Server confidentiality flaw. Oracle says an unauthenticated network attacker could access critical MySQL data, but exploitation is difficult. The affected ranges are MySQL 5.6.42 and earlier, 5.7.24 and earlier, and 8.0.13 and earlier. Exposure is most likely where affected MySQL Server versions are reachable over a network, especially from untrusted networks. Internal-only databases still matter because no privileges are required once network access exists. Prioritize remediation for exposed or sensitive MySQL databases. The vulnerability is not described as easy to exploit, but unauthenticated network access to critical data creates meaningful business risk where affected versions remain reachable. Mitigation focus: Upgrade affected MySQL Server deployments according to Oracle CPU guidance.; Check Oracle and applicable vendor advisories for fixed versions and product-specific instructions.; Restrict MySQL network access to trusted hosts and required application paths..

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-2018-3123 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
2Source 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
Oracle CorporationMySQL Server5.6.42 and prior, 5.7.24 and prior, 8.0.13 and priorListed
Weakness

CWE details

No CWE listed

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