LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2301: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Information Schema).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Information Schema). Supported versions that are affected are 8.0.23 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
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-2301 is a low-severity Oracle MySQL Server issue affecting 8.0.23 and earlier. An already high-privileged attacker with network access could read a limited subset of MySQL data without authorization. This is not a broad unauthenticated compromise scenario, but it matters where privileged database accounts are shared or weakly governed.

Executive priority

Treat this as routine patch and access-control hygiene, not an emergency. Prioritize internet-reachable or broadly accessible MySQL systems and environments with many privileged database users.

Technical view

The flaw is in MySQL Server Information Schema. Oracle rates it CVSS 3.1 2.7 with AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N. Successful exploitation requires high privileges and network access through multiple protocols, with confidentiality-only impact and no stated integrity or availability impact.

Likely exposure

Exposure is limited to Oracle MySQL Server 8.0.23 and prior where high-privileged users can connect over the network. Systems with strict privileged account control, limited database network access, and updated MySQL versions have lower practical risk.

Exploitation context

The source bundle does not identify active exploitation, public exploit use, or CISA KEV listing. Exploitation requires high privileges, so likely scenarios involve insider misuse, compromised administrator credentials, or over-permissioned service accounts.

Researcher notes

Key constraints are high privileges and confidentiality-only impact. The provided sources do not describe the vulnerable query path, proof of concept, or exact fixed release beyond Oracle CPU context, so validation should stay version and configuration based.

Mitigation direction

  • Apply Oracle April 2021 CPU or later MySQL security updates per vendor guidance.
  • Upgrade affected MySQL Server 8.0.23 and earlier deployments where applicable.
  • Restrict network access to MySQL from only approved hosts and services.
  • Review and reduce high-privileged database accounts to least privilege.
  • Check NetApp guidance if MySQL is bundled in relevant NetApp environments.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.23 or earlier.
  • Confirm whether high-privileged accounts can connect over exposed network paths.
  • Review privileged MySQL accounts for unnecessary administrative permissions.
  • Verify installed patch level against Oracle CPU Apr 2021 guidance.
  • Check vendor advisories for packaged or appliance-managed MySQL deployments.
Prepared
Confidence
high
Sources
4

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-2301 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
3Source 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-2301Attack 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.23 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.