LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: InnoDB). Supported versions that are affected are 5.6.34 and earlier5.7.16 and earlier. 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. CVSS v3.0 Base Score 6.5 (Availability impacts).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This MySQL Server flaw can let a low-privileged network attacker crash or hang the database service. The known impact is service outage, not data theft or system takeover. Business urgency depends on whether affected MySQL 5.6 or 5.7 instances support critical applications or are reachable by untrusted networks. Exposure is likely where affected MySQL Server versions remain deployed and reachable by users or systems with low-privileged database access. Internet-facing, partner-facing, or broadly reachable database endpoints raise operational risk. Fully updated Oracle or distribution-packaged MySQL deployments are less likely exposed. Treat as a service availability risk. Prioritize accelerated remediation for critical, customer-facing, or broadly reachable databases. Otherwise, handle through normal vulnerability management with evidence that affected versions are not deployed or are isolated. Mitigation focus: Identify MySQL Server 5.6.34 and earlier, and 5.7.16 and earlier.; Apply Oracle CPU or distribution vendor updates for affected MySQL packages.; Restrict MySQL network access to trusted application 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-2017-3257 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
OracleMySQL Server5.6.34 and earlier, 5.7.16 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.