# CVE-2017-6547: Cross-site scripting in n/a

> Remote attackers can inject arbitrary JavaScript into ASUS routers via long filenames, potentially leading to session hijacking or malicious code execution.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pvx8-88xj-9px8

## What is CVE-2017-6547?

CVE-2017-6547 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in httpd on ASUS RT-N56U, RT-N66U, RT-AC66U, RT-N66R, RT-AC66R, RT-AC68U, RT-AC68R, RT-N66W, RT-AC66W, RT-AC87R, RT-AC87U, RT-AC51U, RT-AC68P, RT-N11P, RT-N12+, RT-N12E B1, RT-AC3200, RT-AC53U, RT-AC1750, RT-AC1900P, RT-N300, and RT-AC750 routers with firmware before 3.0.0.4.380.7378; RT-AC68W routers with firmware before 3.0.0.4.380.7266; and RT-N600, RT-N12+ B1, RT-N11P B1, RT-N12VP B1, RT-N12E C1, RT-N300 B1, and RT-N12+ Pro routers with firmware before 3.0.0.4.380.9488 allows remote attackers to inject arbitrary JavaScript by requesting filenames longer than 50 characters.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Asus Rt-Ac53 Firmware.

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

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

## Is CVE-2017-6547 being exploited?

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

Public exploit code:

- ASUSWRT RT-AC53 (3.0.0.4.380.6038) - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-6548](https://insights.sbomify.com/CVE-2017-6548/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6549](https://insights.sbomify.com/CVE-2017-6549/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6547 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6547 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-6547/ (Markdown: https://insights.sbomify.com/CVE-2017-6547/index.md)
```

## Sources

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

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