# CVE-2017-13772: Memory corruption in n/a

> Remote authenticated attackers can execute arbitrary code on TP-Link WR940N routers via stack-based buffer overflows in specific configuration parameters.

- **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:** 23 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7m3v-jw85-pwvc

## What is CVE-2017-13772?

CVE-2017-13772 is a high-severity memory corruption vulnerability in n/a, published on 23 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in TP-Link WR940N WiFi routers with hardware version 4 allow remote authenticated users to execute arbitrary code via the (1) ping_addr parameter to PingIframeRpm.htm or (2) dnsserver2 parameter to WanStaticIpV6CfgRpm.htm.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-13772?

It affects 1 product.


Products: Tp-Link Wr940n Firmware.

## How do I fix CVE-2017-13772?

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

## Is CVE-2017-13772 being exploited?

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

Public exploit code:

- TP-Link WR940N - (Authenticated) Remote Code (exploitdb)
- TP-Link WDR4300 - Remote Code Execution (Authenticated) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13772 and fix it if it is affected.

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

## Sources

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

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