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

> A remote authenticated attacker can execute arbitrary code with elevated privileges on TP-Link TL-WR940N routers via a stack-based buffer overflow in ICMP handling.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hr74-2752-vc9x

## What is CVE-2019-6989?

CVE-2019-6989 is a high-severity memory corruption vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TP-Link TL-WR940N is vulnerable to a stack-based buffer overflow, caused by improper bounds checking by the ipAddrDispose function. By sending specially crafted ICMP echo request packets, a remote authenticated attacker could overflow a buffer and execute arbitrary code on the system with elevated privileges.

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

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

It affects 2 products.


Products: Tp-Link Tl-Wr940n Firmware, Tp-Link Tl-Wr941nd Firmware.

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

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

## Is CVE-2019-6989 being exploited?

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

Public exploit code:

- TP-LINK TL-WR940N / TL-WR941ND - Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-36355](https://insights.sbomify.com/CVE-2023-36355/): Memory corruption in n/a (critical 9.9)
- [CVE-2022-24355](https://insights.sbomify.com/CVE-2022-24355/): Memory corruption in TL-WR940N (high 8.8)
- [CVE-2026-11409](https://insights.sbomify.com/CVE-2026-11409/): OS Command Injection in IPv6 PPPoE Configuration in TP-Link TL-WR940N (high 8.5)
- [CVE-2026-11410](https://insights.sbomify.com/CVE-2026-11410/): OS Command Injection in BigPond Cable (BPA) Configuration in TP-Link TL-WR940N (high 8.5)
- [CVE-2025-6151](https://insights.sbomify.com/CVE-2025-6151/): TP-Link TL-WR940N, TL-WR841N WanSlaacCfgRpm.htm buffer overflow (high 8.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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