dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21358

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
71/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: Security: Encryption). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows low 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. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 encryption component allows a low-privileged attacker with network access via multiple protocols to cause a denial of service through hang or repeatable crash of the MySQL Server. The attack requires no user interaction and exploits the Server: Security: Encryption component in MySQL 8.0.27 and prior versions.

MitigationApply Oracle's critical patch update for CVE-2022-21358, which involves upgrading MySQL Server to version 8.0.28 or later. If immediate patching is not feasible, restrict network access to MySQL servers and enforce least-privilege principles for database user accounts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify MySQL Server installation and version
    Run 'mysql --version' from command line, or connect to MySQL and execute 'SELECT VERSION();' query
    Affected if The returned version is between 8.0.0 and 8.0.27 inclusive (e.g., 8.0.27, 8.0.25, 8.0.3)
  2. Confirm MySQL service is running
    Check service status via 'systemctl status mysql' or 'service mysql status' on Linux, or check Windows service on Windows systems
    Affected if MySQL service is active and accepting connections while running a vulnerable version
  3. Verify network listening on MySQL port
    Run 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306' to check if MySQL is listening on default port, or verify any configured port via MySQL configuration
    Affected if MySQL is bound to a network interface (0.0.0.0 or specific IP) and reachable over network with a vulnerable version
  4. Check encryption component status
    Connect to MySQL and run 'SHOW VARIABLES LIKE "have_%ssl%";' or 'SHOW VARIABLES LIKE "ssl%";' to see if encryption/SSL/TLS is enabled
    Affected if SSL or encryption features are enabled and the MySQL version is in the vulnerable range (8.0.0-8.0.27)
  5. Identify Netapp products using bundled MySQL
    For Netapp Oncommand Insight or Workflow Automation, check installed product version via web UI or system inventory, then determine bundled MySQL version from product documentation
    Affected if Any version of Netapp Oncommand Insight or Workflow Automation is running, as these bundle MySQL and are listed as affected for all versions

Your environment is affected if you run MySQL Server version 8.0.0 through 8.0.27 (or any version of Netapp Oncommand Insight/Workflow Automation) with network accessibility and the encryption component enabled.

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

Apply Oracle's critical patch update for CVE-2022-21358, which involves upgrading MySQL Server to version 8.0.28 or later. If immediate patching is not feasible, restrict network access to MySQL servers and enforce least-privilege principles for database user accounts.

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-21358 — 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-21358 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