dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-14827

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 8.0.21 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: Security: LDAP Auth). Supported versions that are affected are 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 access to critical data or complete access to all MySQL Server accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

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 LDAP authentication component allows low-privileged attackers with network access to potentially gain unauthorized access to sensitive data. The flaw exists in how MySQL validates LDAP authentication, enabling exploitation via multiple network protocols.

MitigationUpgrade MySQL Server to versions beyond 5.7.31 and 8.0.21 per Oracle's critical patch updates. If LDAP authentication is not required, consider disabling it or restricting network access to trusted networks.

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.31>= 8.0.0, <= 8.0.21
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 the MySQL Server version
    Run `mysql --version` or query `SELECT VERSION();` to obtain the installed MySQL version number
    Affected if The version falls within 5.7.0 to 5.7.31 or 8.0.0 to 8.0.21
  2. Confirm LDAP authentication plugin is loaded
    Query `SHOW PLUGINS;` and look for authentication_ldap_sasl or authentication_ldap_simple plugins with status ACTIVE
    Affected if Either authentication_ldap_sasl or authentication_ldap_simple plugin is active
  3. Check for LDAP authentication configuration
    Query `SELECT user, host, plugin FROM mysql.user WHERE plugin LIKE 'authentication_ldap%';` to see if any users are configured to use LDAP authentication
    Affected if Any users are configured with LDAP-based authentication (authentication_ldap_sasl or authentication_ldap_simple)
  4. Assess network exposure
    Review MySQL bind-address configuration and firewall rules to determine if the MySQL port (3306) is accessible from untrusted networks
    Affected if MySQL is listening on a publicly accessible IP or untrusted network without proper firewall restrictions

You are affected if your MySQL version is 5.7.0-5.7.31 or 8.0.0-8.0.21, the LDAP authentication plugin is active, at least one user is configured to use LDAP authentication, and the MySQL server is reachable from a network where low-privileged attackers could connect.

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

Upgrade MySQL Server to versions beyond 5.7.31 and 8.0.21 per Oracle's critical patch updates. If LDAP authentication is not required, consider disabling it or restricting network access to trusted networks.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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