# CVE-2020-15473: Memory corruption in n/a

> A heap-based buffer over-read in the nDPI OpenVPN dissector allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 1 Jul 2020
- **Updated:** 26 Jan 2026
- **Also known as:** DEBIAN-CVE-2020-15473, GHSA-7c95-7pgx-3px5

## What is CVE-2020-15473?

CVE-2020-15473 is a critical memory corruption vulnerability in n/a, published on 1 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In nDPI through 3.2, the OpenVPN dissector is vulnerable to a heap-based buffer over-read in ndpi_search_openvpn in lib/protocols/openvpn.c.

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

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

It affects 1 product.


Products: Ntop Ndpi.

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

Upgrade to a fixed version.

## Is CVE-2020-15473 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15474](https://insights.sbomify.com/CVE-2020-15474/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-15475](https://insights.sbomify.com/CVE-2020-15475/): Use after free in n/a (critical 9.8)
- [CVE-2020-11939](https://insights.sbomify.com/CVE-2020-11939/): Integer overflow in n/a (critical 9.8)
- [CVE-2020-15471](https://insights.sbomify.com/CVE-2020-15471/): Memory corruption in n/a (critical 9.1)
- [CVE-2021-36082](https://insights.sbomify.com/CVE-2021-36082/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15473 is a critical memory corruption vulnerability in n/a, published on 1 Jul 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-15473 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-15473/ (Markdown: https://insights.sbomify.com/CVE-2020-15473/index.md)
```

## Sources

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

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