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

> Remote attackers can execute arbitrary code on ASUS routers by exploiting a buffer overflow in the networkmap service via crafted SSDP responses.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-45r6-5942-34r7

## What is CVE-2017-11344?

CVE-2017-11344 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Global buffer overflow in networkmap in Asuswrt-Merlin firmware for ASUS devices and ASUS firmware for ASUS RT-AC5300, RT_AC1900P, RT-AC68U, RT-AC68P, RT-AC88U, RT-AC66U, RT-AC66U_B1, RT-AC58U, RT-AC56U, RT-AC55U, RT-AC52U, RT-AC51U, RT-N18U, RT-N66U, RT-N56U, RT-AC3200, RT-AC3100, RT_AC1200GU, RT_AC1200G, RT-AC1200, RT-AC53, RT-N12HP, RT-N12HP_B1, RT-N12D1, RT-N12+, RT_N12+_PRO, RT-N16, and RT-N300 devices allows remote attackers to write shellcode at any address in the heap; this can be used to execute arbitrary code on the router by hosting a crafted device description XML document at a URL specified within a Location header in an SSDP response.

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

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

It affects 28 products.


Products: Asuswrt-Merlin Project Rt-Ac1200 Firmware, Asuswrt-Merlin Project Rt-Ac3100 Firmware, Asuswrt-Merlin Project Rt-Ac3200 Firmware, Asuswrt-Merlin Project Rt-Ac51u Firmware, Asuswrt-Merlin Project Rt-Ac52u Firmware, Asuswrt-Merlin Project Rt-Ac5300 Firmware, Asuswrt-Merlin Project Rt-Ac53 Firmware, Asuswrt-Merlin Project Rt-Ac55u Firmware, Asuswrt-Merlin Project Rt-Ac56u Firmware, Asuswrt-Merlin Project Rt-Ac58u Firmware, Asuswrt-Merlin Project Rt-Ac66u B1 Firmware, Asuswrt-Merlin Project Rt-Ac66u Firmware, Asuswrt-Merlin Project Rt-Ac68p Firmware, Asuswrt-Merlin Project Rt-Ac68u Firmware, Asuswrt-Merlin Project Rt-Ac88u Firmware, Asuswrt-Merlin Project Rt-N12\+ Firmware, Asuswrt-Merlin Project Rt-N12d1 Firmware, Asuswrt-Merlin Project Rt-N12hp B1 Firmware, Asuswrt-Merlin Project Rt-N12hp Firmware, Asuswrt-Merlin Project Rt-N16 Firmware and 8 more.

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

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

## Is CVE-2017-11344 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11420](https://insights.sbomify.com/CVE-2017-11420/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-11345](https://insights.sbomify.com/CVE-2017-11345/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11344 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-11344 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-11344/ (Markdown: https://insights.sbomify.com/CVE-2017-11344/index.md)
```

## Sources

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

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