LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Packaging). 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 require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Server. CVSS v3.0 Base Score 6.7 (Confidentiality, Integrity and Availability impacts).

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

Security readout for executives and security teams

CVE-2017-3312 affects older Oracle MySQL Server packaging. A low-privileged attacker with logon access to the MySQL host could, with another user's interaction, take over MySQL Server. This is not described as remotely exploitable or actively exploited in the provided sources. Exposure is most likely in legacy MySQL deployments, old distribution packages, or systems that still run the affected 5.5, 5.6, or 5.7 versions. Internet exposure alone is not the key condition; attacker logon access to the infrastructure is required. Treat this as a legacy database hygiene issue with meaningful impact but constrained exploitability. Prioritize remediation where old MySQL hosts store sensitive data or allow many infrastructure users to log in. Mitigation focus: Identify MySQL Server versions across production, staging, and legacy hosts.; Apply Oracle CPU guidance or distribution security updates from Red Hat, Debian, or Gentoo.; Prioritize upgrades for systems running MySQL 5.5.53, 5.6.34, 5.7.16, or earlier..

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-3312 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
8Source 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.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.