LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Locking). Supported versions that are affected are 5.5.59 and prior, 5.6.39 and prior and 5.7.21 and prior. Difficult to exploit vulnerability allows high 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. CVSS 3.0 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a denial-of-service flaw in Oracle MySQL Server locking. An attacker already holding high privileges and network access could make vulnerable MySQL versions hang or crash repeatedly. The stated risk is database outage, not data theft or tampering based on the provided CVSS vector. Exposure is most likely where legacy MySQL 5.5, 5.6, or 5.7 instances remain reachable over database protocols by privileged users or service accounts. Internet exposure increases operational concern, but the source requires high privileges, so ordinary unauthenticated scanning is not enough evidence of exploitability. Treat as a planned but meaningful reliability fix. It does not indicate data compromise in the provided sources, but vulnerable database servers could be forced offline by a highly privileged network attacker. Prioritize exposed or business-critical MySQL systems first. Mitigation focus: Apply Oracle or distribution security updates covering the April 2018 MySQL CPU.; Upgrade affected MySQL 5.5, 5.6, and 5.7 deployments beyond the listed vulnerable versions.; Restrict MySQL network access to trusted application hosts and administrative networks..

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-2771 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
15Source 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.5.59 and prior, 5.6.39 and prior, 5.7.21 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.