LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: InnoDB). Supported versions that are affected are 5.6.40 and prior, 5.7.22 and prior and 8.0.11 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.0 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-3064 is a MySQL Server InnoDB flaw that can let a low-privileged network user disrupt the database and modify some accessible data. The main business risk is database outage plus limited unauthorized data changes, not data theft according to the supplied CVSS vector. Exposure is most likely where affected MySQL Server instances accept network connections from application users, service accounts, shared hosting tenants, or other low-privileged database users. Internet exposure raises urgency, but internal-only databases remain relevant if untrusted or broadly shared credentials exist. Treat as high priority for production databases because it combines repeatable outage risk with unauthorized data modification. Prioritize externally reachable, shared, or business-critical MySQL instances first. Mitigation focus: Apply Oracle July 2018 CPU or distribution vendor updates covering CVE-2018-3064.; Upgrade MySQL beyond the affected version ranges listed by Oracle.; 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-3064 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
7Source 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.40 and prior, 5.7.22 and prior, 8.0.11 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.