# CVE-2020-13787: Information disclosure in n/a

> Attackers can intercept sensitive information transmitted in cleartext by D-Link DIR-865L Ax routers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f973-758w-88m4

## What is CVE-2020-13787?

CVE-2020-13787 is a high-severity vulnerability in n/a, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-865L Ax 1.20B01 Beta devices have Cleartext Transmission of Sensitive Information.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Dlink Dir-865l Firmware.

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

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

## Is CVE-2020-13787 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4857](https://insights.sbomify.com/CVE-2013-4857/): Path traversal in n/a (critical 9.8)
- [CVE-2020-13782](https://insights.sbomify.com/CVE-2020-13782/): Command injection in n/a (high 8.8)
- [CVE-2020-13786](https://insights.sbomify.com/CVE-2020-13786/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2013-4855](https://insights.sbomify.com/CVE-2013-4855/): Path traversal in n/a (high 8.8)
- [CVE-2020-13783](https://insights.sbomify.com/CVE-2020-13783/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13787 is a high-severity vulnerability in n/a, published on 3 Jun 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-13787 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-13787/ (Markdown: https://insights.sbomify.com/CVE-2020-13787/index.md)
```

## Sources

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

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