LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3648: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Charsets).

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Charsets). Supported versions that are affected are 5.5.56 and earlier, 5.6.36 and earlier and 5.7.18 and earlier. 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

CVE-2017-3648 is a MySQL Server denial-of-service flaw in charset handling. A highly privileged attacker with network access could cause the database server to hang or repeatedly crash. The business impact is service availability, not data theft, based on the supplied sources. Exposure is most likely in legacy MySQL deployments still running the affected 5.5, 5.6, or 5.7 versions, especially where high-privileged users can connect over the network. Internet exposure increases operational concern, but the source says exploitation is difficult and requires high privileges. Treat this as a moderate availability risk for legacy MySQL systems. It is not described as data compromise, but repeated database crashes can disrupt business services. Prioritize remediation where affected versions support critical applications or permit broad privileged network access. Mitigation focus: Upgrade MySQL Server beyond the affected versions listed by Oracle.; Apply relevant Oracle, Red Hat, or Debian security updates for your deployment.; Restrict MySQL network access to trusted application and administration 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-2017-3648 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
3Source 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.56 and earlier, 5.6.36 and earlier, 5.7.18 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.