dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2020-14663

HIGH · 7.2 CVSS v3.1 Published 2020-07-15
Fix available
A fix is available. Upgrade to after 8.0.20 or later.
See remediation →
78/100
Remediation priority · High
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: Security: Privileges). Supported versions that are affected are 8.0.20 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 takeover of MySQL Server. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 Security:Privileges component affecting versions 8.0.20 and prior. Allows high-privileged attackers with network access to compromise MySQL Server through the privileges subsystem, potentially achieving full takeover. The attack requires high privileges (PR:H) but is network-exploitable (AV:N) with low complexity.

MitigationUpgrade MySQL Server to version 8.0.21 or later. Review user privileges and follow principle of least privilege until patching is complete. Restrict network access to MySQL ports.

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
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 20.04
MySQLDatabase / datastore
Affected:>= 8.0.0, <= 8.0.20
Active Iq Unified ManagerApplication
Affected:all versions
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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 if MySQL Server is installed
    Run 'mysql --version' or 'mysqld --version' on the host to see if MySQL binaries are present. On Ubuntu, also check with 'dpkg -l | grep mysql' or 'snap list' for Snap packages.
    Affected if MySQL Server is found to be installed
  2. Check installed MySQL version
    Connect to MySQL and run 'SELECT @@version;' or use 'mysql --version' from command line. Compare the version number against the affected range: 8.0.0 through 8.0.20.
    Affected if Version is 8.0.20 or earlier (8.0.0 <= version <= 8.0.20)
  3. Verify MySQL network listening configuration
    Check MySQL configuration files (my.cnf or mysqld.cnf) for 'bind-address' setting. Run 'netstat -tlnp | grep 3306' or 'ss -tlnp | grep 3306' to see if MySQL is listening on network interfaces.
    Affected if MySQL is bound to a network address (not 127.0.0.1 only) and is network-accessible
  4. Confirm high-privilege user access
    Connect to MySQL as an administrative user and run 'SELECT user, host, plugin FROM mysql.user;' to list accounts. Check for users with excessive privileges beyond business requirements.
    Affected if Multiple users exist with high privileges (GRANT OPTION, ALL PRIVILEGES) or unnecessary root-level accounts are present

You are affected if MySQL Server 8.0.x (where x <= 20) is installed, is network-accessible, and has high-privilege accounts configured.

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

Upgrade MySQL Server to version 8.0.21 or later. Review user privileges and follow principle of least privilege until patching is complete. Restrict network access to MySQL ports.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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