dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21254

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
59/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. Difficult to exploit 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 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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 Optimizer component (versions 8.0.27 and prior). A low-privileged attacker with network access can exploit this difficult-to-exploit flaw to cause a denial of service by hanging or crashing the MySQL Server.

MitigationApply Oracle's Critical Patch Update for January 2022 or upgrade MySQL Server to version 8.0.28 or later. If immediate patching is not possible, restrict network access to MySQL and follow the principle of least privilege for database 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
FedoraOperating system
Affected:= 34= 35
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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm MySQL Server is installed
    Run 'mysql --version' or check for the mysqld process: 'ps aux | grep mysqld' or check service status: 'systemctl status mysql'
    Affected if MySQL Server is running on the system
  2. Determine the installed MySQL Server version
    Execute 'mysql --version' from command line, or log into MySQL and run 'SELECT VERSION();'
    Affected if Version is between 8.0.0 and 8.0.27 inclusive (for Oracle MySQL)
  3. Verify network accessibility of MySQL
    Check MySQL bind address configuration: review my.cnf for 'bind-address' setting, or test remote connectivity: 'telnet <host> 3306' or 'nc -zv <host> 3306'
    Affected if MySQL is bound to 0.0.0.0 or an externally accessible IP and accepts network connections
  4. Check MySQL user privileges
    Log into MySQL as the application user and run 'SHOW GRANTS;' to identify the privilege level of the account used by the application
    Affected if The application uses a low-privileged account (not root/admin) that has network access to MySQL

The system is affected if MySQL Server version 8.0.0 through 8.0.27 is running and is accessible over the network with any user account.

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

Apply Oracle's Critical Patch Update for January 2022 or upgrade MySQL Server to version 8.0.28 or later. If immediate patching is not possible, restrict network access to MySQL and follow the principle of least privilege for database accounts.

Recommended fix High confidence

MySQL 8.0.28 or later (latest 8.0.x stable release)

  1. 1. Identify the current MySQL Server version using: SELECT VERSION();
  2. 2. For Oracle MySQL: Upgrade to MySQL 8.0.28 or later to obtain the security fix. Download from dev.mysql.com/downloads/mysql/
  3. 3. For Fedora systems: Run 'dnf update mysql' or 'dnf update mariadb' to receive the patched package for Fedora 34/35
  4. 4. For NetApp products (Active Iq Unified Manager, Oncommand Insight, Oncommand Workflow Automation, Snapcenter): Consult NetApp's security advisory at security.netapp.com for product-specific patch availability
  5. 5. After upgrading, verify the new version is running: SELECT VERSION();
  6. 6. Test application functionality to ensure compatibility with the upgraded MySQL version
Caveat MySQL 8.0.28 includes other changes beyond security fixes; review Oracle's release notes for potential compatibility impacts on existing applications

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

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