LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3060: 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.7.22 and prior and 8.0.11 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.0 Base Score 6.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-3060 is an Oracle MySQL Server InnoDB vulnerability affecting MySQL 5.7.22 and earlier, and 8.0.11 and earlier. An attacker already holding high database privileges and network access could alter critical data or crash MySQL. Business urgency is moderate because impact is serious, but exploitation requires privileged access. Exposure is limited to Oracle MySQL Server deployments running 5.7.22 or earlier, or 8.0.11 or earlier. Risk is higher where high-privileged MySQL accounts can connect over the network through supported MySQL protocols. Treat as a scheduled security update priority for affected MySQL environments, with faster handling for internet-reachable or broadly accessible database servers. It is not supported as actively exploited in the provided sources, but it can affect critical data integrity and service availability. Mitigation focus: Identify MySQL Server instances at 5.7.22 or earlier, or 8.0.11 or earlier.; Apply vendor-fixed MySQL updates from Oracle or downstream distribution advisories.; Restrict network access to MySQL from trusted hosts only..

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-3060 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
5Source 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.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.