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

> A buffer overflow in the Tenda router web server allows remote attackers to execute arbitrary code via crafted POST requests.

- **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:** 22 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2j5p-cf62-8pj2

## What is CVE-2020-13390?

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

### Official description

An issue was discovered on Tenda AC6 V1.0 V15.03.05.19_multi_TD01, AC9 V1.0 V15.03.05.19(6318)_CN, AC9 V3.0 V15.03.06.42_multi, AC15 V1.0 V15.03.05.19_multi_TD01, and AC18 V15.03.05.19(6318_)_CN devices. There is a buffer overflow vulnerability in the router's web server -- httpd. While processing the /goform/addressNat entrys and mitInterface parameters for a POST request, a value is directly used in a sprintf to a local variable placed on the stack, which overwrites the return address of a function. An attacker can construct a payload to carry out arbitrary code execution attacks.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 4 products.


Products: Tendacn Ac15 Firmware, Tendacn Ac18 Firmware, Tendacn Ac6 Firmware, Tendacn Ac9 Firmware.

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

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

## Is CVE-2020-13390 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40853](https://insights.sbomify.com/CVE-2022-40853/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-40860](https://insights.sbomify.com/CVE-2022-40860/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-40862](https://insights.sbomify.com/CVE-2022-40862/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-40864](https://insights.sbomify.com/CVE-2022-40864/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-40865](https://insights.sbomify.com/CVE-2022-40865/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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