MySQLDatabase / datastore · Oracle

CVE-2021-2307

MEDIUM · 6.1 CVSS v3.1 Published 2021-04-22
Fix available
A fix is available. Upgrade to after 8.0.23 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Packaging). Supported versions that are affected are 5.7.33 and prior and 8.0.23 and prior. Easily exploitable vulnerability allows unauthenticated attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Vulnerability in MySQL Server's packaging component allows unauthenticated local attackers to potentially gain unauthorized access to critical data after successful human-interaction-based exploitation. The attack requires local logon access to the infrastructure where MySQL executes and human interaction from a person other than the attacker, leading to high confidentiality impact and low integrity impact.

MitigationApply Oracle's patches for MySQL versions 5.7.34+ and 8.0.24+ to address this packaging vulnerability. As this is a local attack vector, ensure strict access controls on systems running MySQL and verify installation package integrity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:>= 8.0.0, <= 8.0.23
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle MySQL Server version
    Run 'mysql --version' or check the MySQL service version via 'mysqld --version' or check the package manager for installed MySQL packages
    Affected if The installed version is greater than or equal to 8.0.0 and less than or equal to 8.0.23
  2. Identify NetApp product installations
    Check for installed NetApp components: look for 'Active Iq Unified Manager', 'Oncommand Insight', 'Oncommand Workflow Automation', or 'Snapcenter' in installed programs or running services
    Affected if Any NetApp product from the affected list (Active Iq Unified Manager, Oncommand Insight, Oncommand Workflow Automation, or Snapcenter) is installed, regardless of version
  3. Verify local access exposure
    Review local user accounts and remote access policies on the system running MySQL or NetApp products
    Affected if The system allows local user logon access by users other than administrators, as the vulnerability requires local logon capability

A system is affected if it runs Oracle MySQL 8.0.0 through 8.0.23, or any version of the listed NetApp products, AND permits local user logon access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 8.0.23
Interim mitigation

Apply Oracle's patches for MySQL versions 5.7.34+ and 8.0.24+ to address this packaging vulnerability. As this is a local attack vector, ensure strict access controls on systems running MySQL and verify installation package integrity.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data