LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3461: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Privileges).

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Privileges). Supported versions that are affected are 5.5.54 and earlier, 5.6.35 and earlier and 5.7.17 and earlier. Easily "exploitable" 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.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/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-3461 is a MySQL Server availability flaw. A highly privileged user who can reach MySQL over the network could make the database hang or crash repeatedly. This is not described as data theft or privilege escalation, but it can disrupt applications that depend on affected MySQL versions. Exposure is mainly legacy MySQL Server deployments on the listed affected versions, especially where privileged database accounts can connect remotely. Systems using vendor-patched Oracle, Debian, or Red Hat packages from the 2017 advisories are less likely to remain exposed. Treat this as a reliability and business-continuity issue for legacy MySQL estates. It is not sourced as actively exploited, but a crashable database can interrupt customer-facing services. Prioritize remediation where affected MySQL hosts support critical applications or allow remote privileged access. Mitigation focus: Apply Oracle or distribution vendor updates for CVE-2017-3461.; Upgrade affected MySQL Server versions beyond the vulnerable releases.; Restrict remote MySQL access to trusted hosts and networks..

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-3461 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.54 and earlier, 5.6.35 and earlier, 5.7.17 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.