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

> Attackers can bypass LDAP authentication in OpenVPN Access Server unless two-factor authentication is enabled, gaining unauthorized access.

- **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:** No
- **Published:** 13 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2x46-5pjx-vpjx

## What is CVE-2020-8953?

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

### Official description

OpenVPN Access Server 2.8.x before 2.8.1 allows LDAP authentication bypass (except when a user is enrolled in two-factor authentication).

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Openvpn Openvpn Access Server.

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

No fix has been published for CVE-2020-8953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8953 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-4234](https://insights.sbomify.com/CVE-2021-4234/): Denial of service in OpenVPN Access Server (high 7.5)
- [CVE-2022-33737](https://insights.sbomify.com/CVE-2022-33737/): Information disclosure in OpenVPN Access Server (high 7.5)
- [CVE-2022-33738](https://insights.sbomify.com/CVE-2022-33738/): Weak cryptography in OpenVPN Access Server (high 7.5)
- [CVE-2020-36382](https://insights.sbomify.com/CVE-2020-36382/): Denial of service in OpenVPN Access Server (high 7.5)
- [CVE-2020-15074](https://insights.sbomify.com/CVE-2020-15074/): Security feature bypass in OpenVPN Access Server (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8953 is a critical authentication bypass vulnerability in n/a, published on 13 Feb 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-8953 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-8953/ (Markdown: https://insights.sbomify.com/CVE-2020-8953/index.md)
```

## Sources

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

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