# CVE-2019-13613: Memory corruption in n/a

> A remote attacker can achieve code execution or cause denial of service via a stack-based buffer overflow in the TP-Link Archer Router's debug protocol.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 17 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-26h2-7ff9-7pj5

## What is CVE-2019-13613?

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

### Official description

CMD_FTEST_CONFIG in the TP-Link Device Debug protocol in TP-Link Wireless Router Archer Router version 1.0.0 Build 20180502 rel.45702 (EU) and earlier is prone to a stack-based buffer overflow, which allows a remote attacker to achieve code execution or denial of service by sending a crafted payload to the listening server.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-13613?

It affects 1 product.


Products: Tp-Link Archer C1200 Firmware.

## How do I fix CVE-2019-13613?

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

## Is CVE-2019-13613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13614](https://insights.sbomify.com/CVE-2019-13614/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-38563](https://insights.sbomify.com/CVE-2023-38563/): Command injection in Archer C1200 (high 8.8)
- [CVE-2020-17891](https://insights.sbomify.com/CVE-2020-17891/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-13134](https://insights.sbomify.com/CVE-2018-13134/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13613 and fix it if it is affected.

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

## Sources

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

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