LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2374: Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.25 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data. CVSS 3.1 Base Score 4.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N).

MediumCVSS 4.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2374 is an Oracle MySQL Server InnoDB vulnerability affecting supported versions 8.0.25 and earlier. It is not an internet-drive-by issue: the attacker needs high privileges and local infrastructure access. The main business risk is confidentiality, including possible access to critical or all MySQL-accessible data.

Executive priority

Treat as a moderate confidentiality risk. It is less urgent than remotely exploitable database flaws, but unpatched MySQL systems with broad administrator access deserve scheduled remediation and access review.

Technical view

The CVSS 3.1 vector is AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N with score 4.1. Sources identify Oracle MySQL Server InnoDB as affected through 8.0.25. No CWE, root-cause detail, exploit procedure, or integrity/availability impact is provided in the bundle.

Likely exposure

Exposure is most likely where Oracle MySQL Server 8.0.25 or earlier remains deployed. Downstream environments using packaged MySQL should check Oracle, Fedora, NetApp, and other vendor advisories for inherited exposure.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation is described as difficult and requires a highly privileged attacker with logon to the infrastructure where MySQL Server runs.

Researcher notes

The bundle lacks root-cause and proof-of-concept detail. Assessment should focus on version exposure, InnoDB presence as part of MySQL Server, local privileged access paths, and whether vendor advisories have been applied.

Mitigation direction

  • Inventory MySQL Server instances and identify versions 8.0.25 or earlier.
  • Apply Oracle July 2021 CPU guidance or current vendor-supported MySQL updates.
  • Check Fedora and NetApp advisories where those platforms package or depend on MySQL.
  • Restrict privileged infrastructure logon paths to MySQL hosts.
  • Review database and host access logs for unusual privileged activity.

Validation and detection

  • Confirm MySQL Server version on each in-scope host.
  • Map each MySQL instance to its vendor package or appliance source.
  • Verify patch status against Oracle July 2021 CPU guidance.
  • Review whether high-privilege local access is tightly limited.
  • Document any unsupported or unpatched MySQL deployments as exceptions.
Prepared
Confidence
high
Sources
6

Public sources used

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-2021-2374 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/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
5Source 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.1CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N0.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.1Medium
CVSS 3.1 vector shape for CVE-2021-2374Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/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 Server8.0.25 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.