dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-2806

MEDIUM · 5.3 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 5.7.29 or later.
See remediation →
59/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: Compiling). Supported versions that are affected are 5.7.28 and prior. Difficult to exploit 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.0 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/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 the MySQL Server 'Compiling' component allows a low-privileged attacker with network access via multiple protocols to cause a denial of service by hanging or crashing the MySQL server repeatedly. The attack is characterized as difficult to exploit (high attack complexity).

MitigationApply the Oracle Critical Patch Update that addresses CVE-2020-2806, or upgrade MySQL Server to a version beyond 5.7.28. Prior to upgrade, conduct compatibility testing in a staging environment.

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.29
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify installed MySQL-related product
    Determine if Oracle MySQL Server or a NetApp product (Active Iq Unified Manager, Oncommand Insight, Oncommand Workflow Automation, or Snapcenter) is running in the environment
    Affected if The product is Oracle MySQL Server or any of the listed NetApp products that bundle MySQL
  2. Check Oracle MySQL Server version
    Run 'mysql --version' from command line or execute 'SELECT VERSION();' in MySQL client to obtain the server version number
    Affected if Version is 5.7.0 through 5.7.28 (inclusive) - that is, version >= 5.7.0 and < 5.7.29
  3. Check NetApp Active Iq Unified Manager version
    Locate the installed version through NetApp documentation, UI, or package management tools
    Affected if Version is >= 7.3 or >= 9.5
  4. Check other NetApp product versions
    Locate the installed version through NetApp documentation, UI, or package management tools for Oncommand Insight, Oncommand Workflow Automation, or Snapcenter
    Affected if Any version is running (these products are listed as affected for all versions)
  5. Verify network accessibility
    Confirm that the MySQL server port (default 3306) is accessible from network segments where untrusted users could connect
    Affected if MySQL is reachable over network from low-privilege users (the vulnerability requires network access via multiple protocols)

You are affected if running Oracle MySQL Server versions 5.7.0 through 5.7.28, or any version of NetApp Active Iq Unified Manager (>= 7.3 or >= 9.5), Oncommand Insight, Oncommand Workflow Automation, or Snapcenter, with network access available to low-privileged attackers.

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.

From vendor data
Upgrade available Upgrade to 5.7.29 or later
Fixed in 5.7.29
Interim mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2020-2806, or upgrade MySQL Server to a version beyond 5.7.28. Prior to upgrade, conduct compatibility testing in a staging environment.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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