CVE-2022-21459
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 · uneditedVulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.28 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 confidenceVulnerability in MySQL Server's Optimizer component allows high-privileged attackers with network access to cause a denial of service (hang or crash) or achieve unauthorized data manipulation (update, insert, delete) on accessible data. The flaw exists in MySQL 8.0.28 and prior versions.
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>= 8.0.0, <= 8.0.28all versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MySQL Server versionRun command: mysql --version or log into MySQL and execute SELECT VERSION();Affected if Version is between 8.0.0 and 8.0.28 inclusive
-
Confirm MySQL is network-accessibleCheck MySQL configuration (my.cnf/my.ini) for bind-address settings, or test remote connectivity on port 3306 (or configured port) from an external hostAffected if MySQL listens on a non-localhost address and is reachable from untrusted networks
-
Verify high-privileged accounts existLog into MySQL and run: SELECT user, host FROM mysql.user WHERE privilege_type IN ('DELETE','UPDATE','INSERT') AND user NOT IN ('mysql.infoschema','mysql.session','mysql.sys');Affected if Any high-privileged MySQL accounts are present (particularly those with DELETE, UPDATE, INSERT privileges)
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the April 2022 Oracle Critical Patch Update for MySQL Server 8.0.29 or later, or upgrade to a supported version. In the interim, restrict network access to MySQL and limit high-privileged accounts to trusted personnel only.
MySQL Server 8.0.29 or later
- 1. Identify all MySQL Server instances running version 8.0.0 through 8.0.28 in your environment
- 2. Review Oracle's Critical Patch Update advisory for April 2022 to obtain the official patch for CVE-2022-21459
- 3. Schedule a maintenance window for the upgrade process
- 4. Back up all MySQL databases before performing the upgrade
- 5. Upgrade MySQL Server to version 8.0.29 or later (the first version containing the fix)
- 6. Verify the upgrade was successful by checking the MySQL Server version and testing application connectivity
- 7. For NetApp products (Active IQ Unified Manager, Oncommand Insight, Snapcenter), monitor NetApp security advisories for product-specific patches as they become available
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21459 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21459 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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