LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2019: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.19 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

LowCVSS 2.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-2019 is a MySQL Server privilege-related flaw that could let an already highly privileged network attacker read some data they should not access. The published impact is limited to confidentiality and carries a low CVSS score.

Executive priority

Treat this as routine but necessary patch and hygiene work, not an emergency. Prioritize internet-reachable or sensitive-data MySQL environments, especially where privileged access is broadly assigned or poorly monitored.

Technical view

Oracle describes the issue in MySQL Server Security: Privileges. Affected supported versions are MySQL Server 8.0.19 and prior. The vector is network-accessible, low attack complexity, no user interaction, but requires high privileges. Impact is limited unauthorized read access.

Likely exposure

Exposure is most likely where MySQL Server 8.0.19 or earlier remains deployed and highly privileged database accounts are reachable over network protocols. Downstream package users should also check Fedora, Gentoo, and NetApp advisories.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. Exploitation requires an attacker who already has high privileges and network access, limiting broad opportunistic risk.

Researcher notes

The key risk constraint is PR:H: the attacker must already hold high privileges. Validation should focus on version exposure, privilege boundaries, and whether vendor patches were applied. The bundle does not provide CWE mapping or exploit details.

Mitigation direction

  • Check Oracle January 2021 CPU guidance for the relevant MySQL Server update path.
  • Update MySQL packages through supported OS or vendor channels where applicable.
  • Restrict network access to MySQL administrative interfaces and privileged accounts.
  • Review and minimize high-privilege database accounts.
  • Check NetApp, Fedora, and Gentoo advisories if those distributions or products are in scope.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.19 or earlier.
  • Confirm installed package versions against Oracle and downstream vendor advisories.
  • Review who has high-privilege MySQL access and from which networks.
  • Check database audit logs for unusual reads by privileged accounts.
  • Document any unsupported or legacy MySQL instances requiring compensating controls.
Prepared
Confidence
high
Sources
7

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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
6Source 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.7CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.7Low
CVSS 3.1 vector shape for CVE-2021-2019Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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