LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3523: Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J).

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-3523 affects Oracle MySQL Connector/J, the Java driver many applications use to connect to MySQL. Oracle rates successful compromise as potentially allowing takeover of the connector, with high confidentiality, integrity, and availability impact. Exploitation is described as difficult and requiring low privileges plus network access. Exposure is most likely in Java applications or platforms bundling MySQL Connector/J 5.1.40 or earlier. Risk is higher where a low-privileged network user can interact with affected connector-driven services. The bundle does not identify specific downstream products. Treat this as a high-priority dependency remediation item, especially for business-critical Java services using MySQL. The vulnerability is older but high impact, so unresolved legacy deployments should be found and upgraded through normal change control. Mitigation focus: Inventory Java dependencies for MySQL Connector/J 5.1.40 or earlier.; Apply Oracle or Debian vendor updates where applicable.; Move affected applications to a vendor-supported fixed connector version..

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-3523 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 Connectors5.1.40 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.