dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-14765

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to 10.1.48 / 10.2.35 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: FTS). Supported versions that are affected are 5.6.49 and prior, 5.7.31 and prior and 8.0.21 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

CVE-2020-14765 is an authenticated denial-of-service vulnerability in Oracle MySQL Server's Full-Text Search (FTS) component. A low-privileged attacker with network access can exploit this vulnerability through malicious FTS queries, causing MySQL Server to hang or crash repeatedly.

MitigationApply the corresponding Oracle Critical Patch Update for MySQL (CPU October 2020) to upgrade to a patched version (5.6.50+, 5.7.32+, or 8.0.22+). Alternatively, restrict network access to MySQL and limit FTS functionality to trusted users until patching can be performed.

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.6.0, <= 5.6.49>= 5.7.0, <= 5.7.31>= 8.0.0, <= 8.0.21
Debian LinuxOperating system
Affected:= 9.0
FedoraOperating system
Affected:= 31= 32= 33
MariaDBDatabase / datastore
Affected:>= 10.1.0, < 10.1.48>= 10.2.0, < 10.2.35>= 10.3.0, < 10.3.26>= 10.4.0, < 10.4.16>= 10.5.0, < 10.5.7
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
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. Confirm MySQL or MariaDB is running
    Check if the MySQL or MariaDB service is active using `systemctl status mysql` or `systemctl status mariadb`, or look for the mysqld process with `ps aux | grep mysql`
    Affected if MySQL or MariaDB server is running and exposed on the network
  2. Identify the installed MySQL version
    Run `mysql --version` from the command line, or connect to the database and execute `SELECT VERSION();`
    Affected if The version is Oracle MySQL 5.6.0 through 5.6.49, 5.7.0 through 5.7.31, or 8.0.0 through 8.0.21
  3. Identify the installed MariaDB version
    Run `mysql --version` from the command line, or connect to the database and execute `SELECT VERSION();`
    Affected if The version is MariaDB 10.1.0 through 10.1.47, 10.2.0 through 10.2.34, 10.3.0 through 10.3.25, 10.4.0 through 10.4.15, or 10.5.0 through 10.5.6
  4. Check if Full-Text Search is enabled or in use
    Query for FULLTEXT indexes by running `SELECT TABLE_SCHEMA, TABLE_NAME FROM information_schema.STATISTICS WHERE INDEX_TYPE = 'FULLTEXT';`
    Affected if Any FULLTEXT indexes exist in the database, indicating FTS is actively used
  5. Verify network accessibility of the MySQL service
    Check the MySQL configuration file (my.cnf or my.ini) for the `bind-address` setting, and test remote connectivity with `nc -zv <host> 3306` or by reviewing firewall rules
    Affected if MySQL is bound to 0.0.0.0 or a publicly routable IP address and is reachable from untrusted networks

Your environment is affected if you are running a vulnerable Oracle MySQL or MariaDB version within the affected ranges and the Full-Text Search feature is enabled and accessible over the network to low-privileged users.

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 10.1.48 / 10.2.35 / 10.3.26 or later
Fixed in 10.1.4810.2.3510.3.26
Interim mitigation

Apply the corresponding Oracle Critical Patch Update for MySQL (CPU October 2020) to upgrade to a patched version (5.6.50+, 5.7.32+, or 8.0.22+). Alternatively, restrict network access to MySQL and limit FTS functionality to trusted users until patching can be performed.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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