LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2933: 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 5.1.48 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.0 Base Score 2.2 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L).

LowCVSS 2.2Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity Oracle MySQL Connector/J issue. A highly privileged network attacker could cause a partial denial of service in affected connector versions. The sources do not indicate data theft, data modification, or active exploitation.

Executive priority

Treat as routine patch management unless the affected connector supports critical service availability. The business risk is service degradation, not confirmed compromise or data exposure.

Technical view

CVE-2020-2933 affects Oracle MySQL Connectors, specifically Connector/J versions 5.1.48 and prior. The CVSS 3.0 score is 2.2 with network attack vector, high attack complexity, high privileges required, no user interaction, and low availability impact only.

Likely exposure

Exposure is limited to environments running MySQL Connector/J 5.1.48 or earlier, including packaged mysql-connector-java distributions referenced by Debian, Fedora, and Gentoo advisories.

Exploitation context

The source bundle describes exploitation as difficult and requiring high privileges plus network access. It is not listed as KEV, and no provided source states active exploitation.

Researcher notes

No CWE is listed, and the source bundle does not provide root-cause detail or exploit mechanics. Analysis should stay focused on version exposure, package provenance, and availability impact.

Mitigation direction

  • Inventory Java applications using MySQL Connector/J or mysql-connector-java packages.
  • Upgrade affected Connector/J 5.1.48-and-prior deployments using Oracle or distribution guidance.
  • Apply relevant Debian, Fedora, Gentoo, or Oracle security updates where applicable.
  • Prioritize systems where connector availability affects customer-facing or operational services.

Validation and detection

  • Check dependency manifests, lockfiles, and runtime classpaths for Connector/J versions 5.1.48 or earlier.
  • Confirm operating system packages include the referenced security update from the relevant distribution.
  • Verify affected applications restart cleanly after connector updates.
  • Review monitoring for partial service failures involving database connectivity.
Prepared
Confidence
high
Sources
8

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-2933 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
Low
CVSS
2.2 (3.0)
Known Exploited
No
Published

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

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
2.2CVSS 3.0LowCVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L0.71.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

2.2Low
CVSS 3.0 vector shape for CVE-2020-2933Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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