# CVE-2024-28820: Memory corruption in n/a

> Attackers with valid LDAP credentials can trigger a buffer overflow in the OpenVPN Auth-LDAP plugin by sending a malformed challenge/response password, potentially causing crashes or code execution.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2024
- **Updated:** 4 Nov 2024
- **Also known as:** ALPINE-CVE-2024-28820, DEBIAN-CVE-2024-28820, GHSA-wv29-6vvq-vc4h, UBUNTU-CVE-2024-28820

## What is CVE-2024-28820?

CVE-2024-28820 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in the extract_openvpn_cr function in openvpn-cr.c in openvpn-auth-ldap (aka the Three Rings Auth-LDAP plugin for OpenVPN) 2.0.4 allows attackers with a valid LDAP username and who can control the challenge/response password field to pass a string with more than 14 colons into this field and cause a buffer overflow.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-28820?


## How do I fix CVE-2024-28820?

Apply the vendor's patch.

## Is CVE-2024-28820 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28820 and fix it if it is affected.

What it is: CVE-2024-28820 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28820 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-2024-28820/ (Markdown: https://insights.sbomify.com/CVE-2024-28820/index.md)
```

## Sources

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

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