FedoraOperating system · Fedoraproject
CVE-2021-2389
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: InnoDB). Supported versions that are affected are 5.7.34 and prior and 8.0.25 and prior. Difficult to exploit vulnerability allows unauthenticated 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.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/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 confidenceCVE-2021-2389 is a denial-of-service vulnerability in the InnoDB storage engine of MySQL Server. Unauthenticated attackers with network access can cause MySQL to hang or crash repeatedly. The vulnerability is rated as difficult to exploit (high attack complexity) and affects MySQL versions 5.7.34 and prior as well as 8.0.25 and prior.
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
= 34= 35
MariaDBDatabase / datastore
>= 10.2.0, < 10.2.40>= 10.3.0, < 10.3.31>= 10.4.0, < 10.4.21>= 10.5.0, < 10.5.12>= 10.6.0, < 10.6.4>= 5.7.0, <= 5.7.34>= 8.0.0, <= 8.0.25all versionsall 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the database product and versionRun 'mysql --version' or 'mariadb --version' on the server, or query 'SELECT VERSION();' via mysql clientAffected if Version is MySQL 5.7.34 or lower, or 8.0.25 or lower, or MariaDB versions 10.2.0-10.2.39, 10.3.0-10.3.30, 10.4.0-10.4.20, 10.5.0-10.5.11, or 10.6.0-10.6.3
-
Check NetApp product installationsOn NetApp systems, verify if Active IQ Unified Manager, Oncommand Insight, Oncommand Workflow Automation, or Snap Center are installed and runningAffected if Any of these NetApp products are present (all versions are affected)
You are affected if you run MySQL 5.7.34 or earlier, MySQL 8.0.25 or earlier, any MariaDB version in the listed ranges, or any NetApp product listed, and the database is network-accessible with InnoDB enabled.
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.
From vendor data10.2.4010.3.3110.4.21
Apply Oracle's Critical Patch Update for July 2021 or upgrade MySQL to a version beyond 8.0.25 (for 8.0 branch) or 5.7.35+ (for 5.7 branch). Restrict network access to MySQL ports as an interim compensating control.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2389 — 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-2021-2389 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