dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21378

MEDIUM · 5.5 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

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: Optimizer). Supported versions that are affected are 8.0.27 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 ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).

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 · high confidence

This vulnerability exists in the MySQL Server Optimizer component. A high-privileged attacker with network access can cause a denial of service (hang or crash) and gain unauthorized insert, update, or delete access to some accessible data. The attack requires existing database privileges but can be exploited remotely via multiple network protocols.

MitigationUpgrade MySQL Server to version 8.0.28 or later to obtain the security fix. If immediate upgrade is not feasible, restrict network access to the database and limit privileged user access as a compensating control.

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.27
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

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

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. Check MySQL Server version
    Run command: mysql -V or log into MySQL and execute SELECT VERSION();
    Affected if Version is between 8.0.0 and 8.0.27 inclusive
  2. Check for NetApp Oncommand Insight installation
    Inspect system for installed Oncommand Insight software - check installed programs on Windows or package manager on Linux
    Affected if Oncommand Insight is installed (all versions are affected)
  3. Check for NetApp Oncommand Workflow Automation installation
    Inspect system for installed Oncommand Workflow Automation software - check installed programs on Windows or package manager on Linux
    Affected if Oncommand Workflow Automation is installed (all versions are affected)
  4. Verify network accessibility to MySQL
    Check MySQL bind-address configuration and firewall rules to determine if network access is possible from untrusted networks
    Affected if MySQL is accessible over network to untrusted users (network access is required for the attack)
  5. Audit high-privileged MySQL accounts
    Query MySQL for users with high privileges: SELECT user, host FROM mysql.user WHERE Super_priv='Y' OR privileges include INSERT/UPDATE/DELETE on sensitive tables
    Affected if There are high-privileged accounts accessible over network (the attacker needs existing database privileges to exploit)

You are affected if you run MySQL 8.0.0-8.0.27 OR have NetApp Oncommand Insight/Workflow Automation installed, AND your MySQL is network-accessible with high-privileged accounts present.

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.27
Interim mitigation

Upgrade MySQL Server to version 8.0.28 or later to obtain the security fix. If immediate upgrade is not feasible, restrict network access to the database and limit privileged user access as a compensating control.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2022-21378 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