dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21635

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to after 8.0.29 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: InnoDB). 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 creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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 InnoDB storage engine allows high privileged attackers with network access to modify or delete critical data and cause denial of service. The flaw affects MySQL 8.0.29 and prior versions.

MitigationUpgrade MySQL Server to version 8.0.30 or later to receive the patch. As a defense-in-depth measure, restrict network access to MySQL and follow least-privilege principles 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, <= 8.0.29
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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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' from command line, or connect to MySQL and execute 'SELECT VERSION();' or 'SELECT @@version;'. Compare the output to the affected range 8.0.0 through 8.0.29.
    Affected if The version is 8.0.x where x is 29 or lower.
  2. Confirm InnoDB storage engine is in use
    Connect to MySQL and run 'SHOW ENGINES;' to list available engines, then 'SHOW VARIABLES LIKE 'default_storage_engine';' to see the default.
    Affected if InnoDB is enabled (it is the default in MySQL 8.0).
  3. Verify network accessibility to MySQL
    Check MySQL bind-address configuration by running 'SHOW VARIABLES LIKE 'bind_address';' and test external connectivity (e.g., 'telnet <host> 3306' or 'nc -zv <host> 3306').
    Affected if MySQL is listening on a non-localhost interface and is accessible from untrusted networks.
  4. Check user privileges
    Connect to MySQL and run 'SHOW GRANTS FOR CURRENT_USER();' to identify if the account has high privileges.
    Affected if The account has privileges beyond standard user access (e.g., root, DBA-level privileges).

You are affected if you run MySQL 8.0.29 or earlier with InnoDB enabled and have network accessibility from untrusted sources, especially with high-privileged accounts.

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 version 8.0.30 or later to receive the patch. As a defense-in-depth measure, restrict network access to MySQL and follow least-privilege principles for database accounts.

Recommended fix High confidence

MySQL 8.0.30 or later (8.0.x series)

  1. Back up all MySQL databases before performing any upgrade
  2. Review MySQL 8.0.30 release notes and upgrade documentation at dev.mysql.com/doc/refman/8.0/en/upgrading.html
  3. Ensure application compatibility with MySQL 8.0.30 by testing in a non-production environment
  4. Schedule a maintenance window for the upgrade procedure
  5. Stop all MySQL services and applications connecting to the database
  6. Upgrade MySQL Server from 8.0.x to 8.0.30 or later using your system's package manager or MySQL installer
  7. Verify the upgrade was successful by checking the MySQL server version: SELECT VERSION();
  8. Start MySQL services and verify all databases are accessible
Caveat Review MySQL 8.0 release notes for any configuration or behavior changes between your current version and 8.0.30; test thoroughly in staging before production deployment

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

Fix this in MySQL Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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