dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21367

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: Compiling). Supported versions that are affected are 5.7.36 and prior and 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

Vulnerability in MySQL Server's Server:Compiling component allows a high-privileged attacker with network access to cause a denial of service (complete server hang or crash) or achieve unauthorized insert/update/delete access to some MySQL Server data. The attack requires high privileges but has low complexity and no user interaction required.

MitigationUpgrade MySQL Server to a version beyond 5.7.36 and 8.0.27 to obtain the security patch for this vulnerability.

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:>= 5.7.0, <= 5.7.36>= 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. Determine installed MySQL Server version
    Run 'mysql --version' or log into MySQL and execute 'SELECT VERSION();'
    Affected if Version is between 5.7.0 and 5.7.36, or between 8.0.0 and 8.0.27
  2. Identify NetApp Oncommand Insight installation
    Check system for installed Oncommand Insight software using package manager or installed programs listing
    Affected if Oncommand Insight is present on the system (all versions are affected)
  3. Identify NetApp Oncommand Workflow Automation installation
    Check system for installed Oncommand Workflow Automation software using package manager or installed programs listing
    Affected if Oncommand Workflow Automation is present on the system (all versions are affected)
  4. Verify MySQL user privileges
    Log into MySQL and run 'SELECT user, host, plugin FROM mysql.user;' to list users and their authentication method, then check which users have high-privilege roles (root, admin, or those with GRANT ALL)
    Affected if High-privileged MySQL accounts exist that could be exploited by an attacker
  5. Check MySQL network exposure
    Review MySQL configuration files (my.cnf or my.ini) for 'bind-address' setting and firewall rules to determine if MySQL port 3306 is accessible from network
    Affected if MySQL is listening on a network-accessible interface (not bound to localhost/127.0.0.1)

You are affected if you run MySQL Server versions 5.7.0-5.7.36 or 8.0.0-8.0.27, or if you have NetApp Oncommand Insight or Oncommand Workflow Automation installed, and an attacker with high privileges can access your MySQL server over the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.27
Interim mitigation

Upgrade MySQL Server to a version beyond 5.7.36 and 8.0.27 to obtain the security patch for this vulnerability.

Recommended fix High confidence

MySQL 5.7.37+ (5.7.x) or MySQL 8.0.28+ (8.0.x)

  1. 1. Backup all MySQL databases before upgrading
  2. 2. Stop the MySQL Server service
  3. 3. For MySQL 5.7.x: Upgrade to MySQL 5.7.37 or later (recommended: 5.7.x latest stable)
  4. 4. For MySQL 8.0.x: Upgrade to MySQL 8.0.28 or later (recommended: 8.0.x latest stable)
  5. 5. Verify the upgrade by checking MySQL version: SELECT VERSION();
  6. 6. Test application connectivity and functionality
  7. 7. Restart the MySQL Server service
Caveat Minor version upgrades typically maintain backward compatibility; review Oracle MySQL 5.7.37 and 8.0.28 release notes for any specific behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21367 — 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-21367 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