dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21454

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to after 8.0.28 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: Group Replication Plugin). Supported versions that are affected are 5.7.37 and prior and 8.0.28 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 Group Replication Plugin allows a low-privileged attacker with network access to cause a denial of service by crashing or hanging the MySQL Server. The flaw exists in versions 5.7.37 and prior and 8.0.28 and prior.

MitigationApply the relevant Oracle MySQL critical patch update that addresses this vulnerability in the Group Replication Plugin component, updating to a version beyond 8.0.28 or 5.7.37 as appropriate.

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:>= 5.7.0, <= 5.7.37>= 8.0.0, <= 8.0.28
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
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
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. Check installed MySQL Server version
    Run `mysql --version` or query `SELECT VERSION();` to get the exact version number
    Affected if Version is 5.7.37 or prior, or 8.0.28 or prior (within 5.7.0-5.7.37 or 8.0.0-8.0.28 ranges)
  2. Verify Group Replication plugin is loaded
    Run query `SHOW PLUGINS;` and look for 'group_replication' plugin status, or check `SELECT * FROM information_schema.PLUGINS WHERE PLUGIN_NAME LIKE 'group_replication';`
    Affected if Plugin status is ACTIVE and the MySQL version falls within the affected ranges
  3. Check if Group Replication is actively configured
    Examine MySQL configuration files (my.cnf or my.ini) for `group_replication` settings, or run `SHOW VARIABLES LIKE 'group_replication%';`
    Affected if Group Replication is enabled in configuration and version is within affected ranges
  4. For NetApp products, identify if affected MySQL component exists
    Check NetApp product documentation or installed components for presence of MySQL Server with Group Replication capability
    Affected if Any NetApp Active IQ Unified Manager, Oncommand Insight, or Snapcenter version is installed (all versions affected)

Environment is affected if running Oracle MySQL 5.7.0-5.7.37 or 8.0.0-8.0.28 with Group Replication plugin enabled, or if any NetApp product listed is installed regardless of version

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

Apply the relevant Oracle MySQL critical patch update that addresses this vulnerability in the Group Replication Plugin component, updating to a version beyond 8.0.28 or 5.7.37 as appropriate.

Recommended fix High confidence

MySQL 5.7.38+ or 8.0.29+ (depending on your major version)

  1. 1. Back up the MySQL database before performing any upgrade.
  2. 2. For MySQL 5.7.x: Upgrade MySQL Server to version 5.7.38 or later.
  3. 3. For MySQL 8.0.x: Upgrade MySQL Server to version 8.0.29 or later.
  4. 4. Verify the Group Replication Plugin version after upgrade using: SELECT PLUGIN_NAME, PLUGIN_VERSION FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME = 'group_replication';
  5. 5. Test Group Replication functionality in a non-production environment before deploying to production.
  6. 6. Restart MySQL service after upgrade if not done automatically by package manager.
Caveat Always review MySQL upgrade notes before upgrading; minor upgrades within the same major version are typically safe but test in staging first

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

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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