CVE-2017-3313: Oracle MySQL Server vulnerability

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: MyISAM). Supported versions that are affected are 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data. CVSS v3.0 Base Score 4.7 (Confidentiality impacts).

UnknownCVSS not scoredNot KEV-listedUpdatedOct 8, 2024, 20:34 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2017-3313 affects Oracle MySQL Server’s MyISAM component. An attacker with low privileges and logon access to the server infrastructure could gain unauthorized access to critical MySQL data. The issue is hard to exploit, but exposed legacy MySQL systems can still create sensitive data risk. Exposure is most likely on legacy Oracle MySQL deployments still running affected 5.5, 5.6, or 5.7 builds, especially where low-privileged users can log on to infrastructure hosting MySQL. Systems using MyISAM tables deserve particular review. Treat as a legacy database hygiene issue with confidentiality risk. It is not presented as actively exploited, but old MySQL servers holding sensitive data should be upgraded or isolated promptly. Mitigation focus: Identify MySQL servers at or below the affected versions.; Apply Oracle or distribution vendor updates from the cited advisories.; Prioritize internet-facing or shared-hosting database infrastructure..

Prepared: Jun 13, 2026, 12:51 UTC (UTC+00:00)

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-3313 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: Jan 27, 2017, 22:01 UTC (UTC+00:00)

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

CVE List V5 sourceCVE List V5
RHSA-2017:2787CVE reference · vendor-advisory, x_refsource_REDHAT
GLSA-201702-17CVE reference · vendor-advisory, x_refsource_GENTOO
RHSA-2018:0574CVE reference · vendor-advisory, x_refsource_REDHAT
RHSA-2018:0279CVE reference · vendor-advisory, x_refsource_REDHAT
RHSA-2017:2886CVE reference · vendor-advisory, x_refsource_REDHAT
RHSA-2017:2192CVE reference · vendor-advisory, x_refsource_REDHAT

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

OracleMySQL Server5.5.53 and earlier, 5.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.