Percona ServerApplication · Percona

CVE-2020-26542

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-09
Fix available
A fix is available. Upgrade to after 2020-10-02 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in the MongoDB Simple LDAP plugin through 2020-10-02 for Percona Server when using the SimpleLDAP authentication in conjunction with Microsoft’s Active Directory, Percona has discovered a flaw that would allow authentication to complete when passing a blank value for the account password, leading to access against the service integrated with which Active Directory is deployed at the level granted to the authenticating account.

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 · moderate confidence

The MongoDB Simple LDAP plugin for Percona Server contains an authentication bypass vulnerability when used with Microsoft Active Directory. The flaw allows authentication to succeed even when a blank password is provided, effectively bypassing the password verification mechanism and granting access with the privileges of the authenticating Active Directory account.

MitigationOrganizations using the Simple LDAP plugin with Active Directory should immediately review authentication configurations and consider implementing additional controls such as account lockout policies or multi-factor authentication until a patch is available from Percona.

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
Percona ServerApplication
Affected:<= 2020-10-02

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Percona Server version
    Run 'mysqld --version' or check the installed Percona Server package to determine the version date (format is typically YYYY-MM-DD)
    Affected if The version date is 2020-10-02 or earlier
  2. Locate Simple LDAP plugin configuration
    Check MySQL configuration files (my.cnf or mysqld.cnf) for entries containing 'auth_ldap_simple' or 'plugin-load-add' that load the Simple LDAP authentication plugin
    Affected if The Simple LDAP plugin is loaded via plugin-load-add or similar directive
  3. Verify Active Directory is the LDAP backend
    Examine LDAP configuration parameters in my.cnf or mysqld.cnf under sections related to auth_ldap_simple, specifically looking for LDAP server settings that connect to Microsoft Active Directory domain controllers
    Affected if The LDAP configuration points to Active Directory domain controllers (typically uses port 389 or 636, with domain-style DN strings)
  4. Test blank password authentication behavior
    Attempt to authenticate to MySQL using an Active Directory user account with an empty or blank password string against the Simple LDAP plugin
    Affected if Authentication succeeds with a blank password when it should fail, indicating the bypass is present

A Percona Server installation dated 2020-10-02 or earlier with the Simple LDAP plugin enabled and configured for Active Directory is vulnerable to blank password authentication bypass.

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 2020-10-02
Interim mitigation

Organizations using the Simple LDAP plugin with Active Directory should immediately review authentication configurations and consider implementing additional controls such as account lockout policies or multi-factor authentication until a patch is available from Percona.

Fix this in Percona Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26542 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-26542 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