LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3469: Vulnerability in the MySQL Workbench component of Oracle MySQL (subcomponent: Workbench: Security : Encrypt...

Vulnerability in the MySQL Workbench component of Oracle MySQL (subcomponent: Workbench: Security : Encryption). Supported versions that are affected are 6.3.8 and earlier. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Workbench. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Workbench accessible data. CVSS 3.0 Base Score 3.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

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

Security readout for executives and security teams

CVE-2017-3469 is a confidentiality issue in Oracle MySQL Workbench 6.3.8 and earlier. An unauthenticated network attacker could read some Workbench-accessible data, but Oracle rated exploitation as difficult and the impact as limited. Treat this mainly as legacy software risk. Exposure is limited to environments still using MySQL Workbench 6.3.8 or earlier. The bundle does not establish internet-facing exposure, server-side MySQL impact, or affected versions beyond the listed Workbench releases. Low priority unless old MySQL Workbench versions remain in environments handling sensitive database access. The business risk is mainly unauthorized reading of limited Workbench-accessible data, not system takeover or service disruption based on the provided evidence. Mitigation focus: Inventory MySQL Workbench installations and identify versions 6.3.8 or earlier.; Review Oracle's April 2017 Critical Patch Update for vendor remediation guidance.; Upgrade or retire affected Workbench versions according to Oracle guidance..

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-3469 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
1Source 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 Workbench6.3.8 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.