# CVE-2020-26542: Auth bypass in n/a

> Attackers can bypass authentication in Percona Server's Simple LDAP plugin by providing a blank password when using Active Directory.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q88m-4hg8-4h3h, MINI-28vr-7244-9fwp, MINI-9f67-wpjv-2wh8, MINI-9qpv-392w-8rvp

## What is CVE-2020-26542?

CVE-2020-26542 is a critical authentication bypass vulnerability in n/a, published on 9 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-26542?

It affects 1 product.


Products: Percona Percona Server.

## How do I fix CVE-2020-26542?

Apply the vendor's patch.

## Is CVE-2020-26542 being exploited?

There is no known exploitation of CVE-2020-26542 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-12301](https://insights.sbomify.com/CVE-2019-12301/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-34968](https://insights.sbomify.com/CVE-2022-34968/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26542 and fix it if it is affected.

What it is: CVE-2020-26542 is a critical authentication bypass vulnerability in n/a, published on 9 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26542 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26542/ (Markdown: https://insights.sbomify.com/CVE-2020-26542/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26542
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26542
- OSV: https://osv.dev/vulnerability/CVE-2020-26542

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26542/
Summaries are generated and may contain mistakes; the official description above is the record.