dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-21509

MEDIUM · 5.5 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to after 8.0.29 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.29 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 is a vulnerability in the MySQL Server Optimizer component affecting versions 8.0.29 and prior. A high-privileged attacker with network access can exploit this to cause a denial of service (hang or repeatable crash) and gain unauthorized insert, update, or delete access to some MySQL data.

MitigationUpgrade MySQL Server to a version beyond 8.0.29 that includes the security patch, typically available through Oracle's Critical Patch Updates.

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
FedoraOperating system
Affected:= 35
Mysql ServerDatabase / datastore
Affected:<= 8.0.29
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
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 'mysql --version' or query 'SELECT VERSION();' to obtain the installed MySQL Server version.
    Affected if The version is 8.0.29 or lower.
  2. Verify Optimizer component is in use
    MySQL Optimizer is a core component of the MySQL Server query processing pipeline. Check for recent query execution plans using 'EXPLAIN' on complex queries, or review slow query logs that involve join optimization.
    Affected if The Optimizer is actively processing queries, which is default behavior in MySQL 8.0.x.
  3. Assess network accessibility
    Determine if MySQL server is bound to network interfaces (check my.cnf for 'bind-address' setting and verify listening ports with 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306').
    Affected if MySQL is listening on a network-accessible interface (0.0.0.0 or specific IP) rather than localhost only.
  4. Check NetApp product MySQL backend versions
    For NetApp products (Active Iq Unified Manager, Oncommand Insight, Oncommand Workflow Automation, Snapcenter), review the bundled MySQL version or the MySQL instance used by the NetApp application.
    Affected if The NetApp product uses a MySQL backend at version 8.0.29 or lower.

A user is affected if their MySQL Server installation is version 8.0.29 or lower and is network-accessible, or if their NetApp product bundles a MySQL version within this range.

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

Upgrade MySQL Server to a version beyond 8.0.29 that includes the security patch, typically available through Oracle's Critical Patch Updates.

Recommended fix High confidence

MySQL Server 8.0.30 or later

  1. 1. Backup all MySQL databases before upgrading
  2. 2. For Oracle MySQL Server: Upgrade MySQL Server to version 8.0.30 or later which contains the security fix
  3. 3. For Fedora 35 systems: Run 'sudo dnf update mysql' or 'sudo dnf update' to apply available security updates containing the fixed MySQL packages
  4. 4. After upgrading, restart the MySQL service: 'sudo systemctl restart mysqld'
  5. 5. Verify the new MySQL version using: 'mysql --version' or 'SELECT VERSION();'
  6. 6. For NetApp products (Active Iq Unified Manager, Oncommand Insight, Oncommand Workflow Automation, Snapcenter): Contact NetApp support for product-specific security updates as these products bundle MySQL
Caveat Minor version upgrades within 8.0.x typically have low risk but always test in staging first; review Oracle's MySQL 8.0.30 release notes for any optimizer changes that may affect query plans

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

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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