LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3291: 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 high 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.3 (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-3291 affects older Oracle MySQL Server releases. It is not described as remotely exploitable by an unauthenticated attacker; the source says exploitation is difficult, requires high privileges on the MySQL host infrastructure, and needs another person to interact. Successful exploitation can still result in takeover of MySQL Server. Exposure is mainly legacy MySQL Server installations at or below 5.5.53, 5.6.34, or 5.7.16. Risk is higher where administrators, operators, automation, or package-management processes interact with MySQL packaging on systems reachable by high-privileged users. Handle as a legacy database patching and access-control issue. It is not marked actively exploited, but the consequence is MySQL Server takeover. Prioritize systems that are old, business-critical, internet-adjacent, or administered by many privileged users. Mitigation focus: Apply Oracle or distribution security updates for affected MySQL packages.; Upgrade MySQL beyond the affected version ranges listed by Oracle.; Prioritize legacy servers with administrative multi-user access..

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-3291 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
n/aMySQL Server 5.5.53andearlier;5.6.34andearlier;5.7.16andearlierMySQL Server 5.5.53andearlier;5.6.34andearlier;5.7.16andearlierListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.