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

> Unauthenticated attackers can inject persistent scripts into Arris TG1682G modems via the service parameter, potentially hijacking user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wfv9-xvh7-763f

## What is CVE-2017-16836?

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

Arris TG1682G devices with Comcast TG1682_2.0s7_PRODse 10.0.59.SIP.PC20.CT software allow Unauthenticated Stored XSS via the actionHandler/ajax_managed_services.php service parameter.

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

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

It affects 1 product.


Products: Commscope Arris Tg1682g Firmware.

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

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

## Is CVE-2017-16836 being exploited?

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

Public exploit code:

- Arris TG1682G Modem - Persistent Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-10990](https://insights.sbomify.com/CVE-2018-10990/): Security feature bypass in n/a (high 8.0)
- [CVE-2018-10989](https://insights.sbomify.com/CVE-2018-10989/): Hardcoded credentials in n/a (medium 6.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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