dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-2768

MEDIUM · 6.3 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 8.0.19 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable

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 Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.3.28 and prior, 7.4.27 and prior, 7.5.17 and prior, 7.6.13 and prior and 8.0.19 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Cluster as well as unauthorized update, insert or delete access to some of MySQL Cluster accessible data. CVSS 3.0 Base Score 6.3 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/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 confidence

This is a vulnerability in MySQL Cluster's general cluster component affecting versions 7.3.28 and prior, 7.4.27 and prior, 7.5.17 and prior, 7.6.13 and prior, and 8.0.19 and prior. It allows low-privileged attackers with network access to cause a complete denial of service (hang or crash) and gain unauthorized insert, update, or delete access to some cluster data. Exploitation requires human interaction.

MitigationApply the appropriate Oracle Critical Patch Update (CPU) for this vulnerability and upgrade to a patched version of MySQL Cluster (8.0.20+ or the corresponding patched 7.x release).

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:>= 7.3.0, <= 7.3.28>= 7.4.0, <= 7.4.27>= 7.5.0, <= 7.5.17>= 7.6.0, <= 7.6.13>= 8.0.0, <= 8.0.19
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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MySQL Cluster is installed
    Look for ndb_mgmd (management node), ndbd (data node), or ndbapi processes running, or check for presence of ndb* binaries in standard MySQL directories (e.g., /usr/local/mysql/bin, /opt/mysql/). On Linux: ps aux | grep ndb or which ndb_mgmd.
    Affected if MySQL Cluster processes or binaries are found on the system.
  2. Determine the MySQL Cluster version
    Run 'ndb_mgmd --version' or 'mysql --version' on a node with MySQL client tools. For management nodes, check the version from ndb_mgmd output. Compare against affected ranges: 7.3.0-7.3.28, 7.4.0-7.4.27, 7.5.0-7.5.17, 7.6.0-7.6.13, 8.0.0-8.0.19.
    Affected if The installed version falls within any of the affected version ranges.
  3. Verify network exposure of cluster services
    Check if MySQL Cluster management (port 1186) or SQL node (port 3306) ports are listening on non-loopback interfaces. Run 'netstat -tlnp | grep -E "(3306|1186)"' or 'ss -tlnp | grep -E "(3306|1186)"'. Confirm the listening address with 'netstat -tlnp' and check if bound to 0.0.0.0 or a non-local IP.
    Affected if Cluster ports are exposed to network interfaces reachable by low-privileged network attackers.
  4. Check for NetApp Active IQ Unified Manager installations
    If the system runs NetApp Active IQ Unified Manager (formerly Oncommand Unified Manager), check the installed version. On Linux: rpm -qi oiufm or check /opt/netapp/um/version. Compare version against >= 7.3 or >= 9.5.
    Affected if NetApp Active IQ Unified Manager version 7.3+ or 9.5+ is installed.
  5. Identify other affected NetApp products
    Check for presence of NetApp Oncommand Insight, Oncommand Workflow Automation, or SnapCenter installations. These are affected at all versions per the advisory. Look for process names or installed packages: 'snapcenter', 'oci', 'oncommand'. Use 'dpkg -l' or 'rpm -qa' to list installed packages.
    Affected if Any of these NetApp products are installed on the system.

You are affected if MySQL Cluster is installed with a version in the 7.3.x through 8.0.19 range and is network-accessible, or if any NetApp product listed (Active IQ Unified Manager, Oncommand Insight, Oncommand Workflow Automation, SnapCenter) is installed.

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 a release after 8.0.19
Interim mitigation

Apply the appropriate Oracle Critical Patch Update (CPU) for this vulnerability and upgrade to a patched version of MySQL Cluster (8.0.20+ or the corresponding patched 7.x release).

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-2768 — 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-2768 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