LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2875: Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J).

Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.14 and prior and 5.1.48 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data. CVSS 3.0 Base Score 4.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N).

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-2875 affects Oracle MySQL Connector/J used by applications to connect to MySQL. An unauthenticated network attacker may cause limited unauthorized reads and data changes, but exploitation is rated difficult and requires human interaction. Business urgency is moderate, focused on systems still carrying old connector libraries.

Executive priority

Treat as a moderate dependency remediation item. It is not a confirmed exploited emergency, but legacy database connector libraries can sit inside business applications for years and may affect data integrity and confidentiality.

Technical view

Oracle describes a Connector/J flaw in MySQL Connectors versions 8.0.14 and prior and 5.1.48 and prior. CVSS 3.0 is 4.7: network attack vector, high complexity, no privileges, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely in Java applications, packaged services, or Linux distributions that include old mysql-connector-java or MySQL Connector/J dependencies. Internet exposure depends on how the application uses the connector and whether an attacker can reach the relevant service path.

Exploitation context

The supplied sources do not report active exploitation, and the bundle marks KEV as false. Oracle says exploitation is difficult, unauthenticated, network reachable, and requires user interaction by someone other than the attacker. Details are insufficient to infer a reliable exploitation pattern.

Researcher notes

Public detail in the supplied sources is limited to product, affected versions, CVSS, impact, and advisory links. Avoid assuming root cause or exploit mechanics. Validation should focus on dependency discovery across application artifacts and distribution package status.

Mitigation direction

  • Upgrade MySQL Connector/J using Oracle April 2020 CPU guidance.
  • Apply Debian, Fedora, or Gentoo mysql-connector-java security updates where applicable.
  • Inventory applications bundling Connector/J, not only operating-system packages.
  • Prioritize services handling sensitive or regulated database records.
  • Check vendor guidance if fixed package versions are unclear.

Validation and detection

  • Search dependency manifests for MySQL Connector/J or mysql-connector-java.
  • Confirm no deployed version is 8.0.14, 5.1.48, or earlier.
  • Check container images and shaded Java archives for bundled connector copies.
  • Verify distribution security advisories are applied on managed hosts.
  • Record compensating controls if immediate upgrade is blocked.
Prepared
Confidence
medium
Sources
6

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-2020-2875 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
Medium
CVSS
4.7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.0MediumCVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N1.62.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4.7Medium
CVSS 3.0 vector shape for CVE-2020-2875Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Connectors8.0.14 and prior, 5.1.48 and priorListed
Weakness

CWE details

No CWE listed

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