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

> Persistent XSS in Technicolor routers allows attackers to poison DNS and steal credentials via malicious SSIDs.

- **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:** 3 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rr6p-9rm4-m6j5

## What is CVE-2017-11320?

CVE-2017-11320 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Aug 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

Persistent XSS through the SSID of nearby Wi-Fi devices on Technicolor TC7337 routers 08.89.17.20.00 allows an attacker to cause DNS Poisoning and steal credentials from the router.

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

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

It affects 1 product.


Products: Technicolor Tc7337 Firmware.

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

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

## Is CVE-2017-11320 being exploited?

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

Public exploit code:

- Technicolor TC7337 - 'SSID' Persistent Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-11449](https://insights.sbomify.com/CVE-2020-11449/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11320 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Aug 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-11320 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-11320/ (Markdown: https://insights.sbomify.com/CVE-2017-11320/index.md)
```

## Sources

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

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