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

> Remote attackers can execute arbitrary code on ASUS routers by sending a crafted HTTP GET request with a long parameter, requiring firmware updates.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 9 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5373-xwjx-wwr9

## What is CVE-2017-12754?

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

### Official description

Stack buffer overflow in httpd in Asuswrt-Merlin firmware 380.67_0RT-AC5300 and earlier 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 execute arbitrary code on the router by sending a crafted http GET request packet that includes a long delete_offline_client parameter in the url.

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

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

It affects 1 product.


Products: Asuswrt-Merlin Asuswrt-Merlin.

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

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

## Is CVE-2017-12754 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5721](https://insights.sbomify.com/CVE-2018-5721/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12754 is a high-severity memory corruption vulnerability in n/a, published on 9 Aug 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-12754 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-12754/ (Markdown: https://insights.sbomify.com/CVE-2017-12754/index.md)
```

## Sources

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

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