# CVE-2014-9021: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via multiple parameters in ZTE ZXDSL 831 interfaces, requiring user interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mrg2-8f7m-jw7f

## What is CVE-2014-9021?

CVE-2014-9021 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in ZTE ZXDSL 831 allow remote attackers to inject arbitrary web script or HTML via the (1) tr69cAcsURL, (2) tr69cAcsUser, (3) tr69cAcsPwd, (4) tr69cConnReqPwd, or (5) tr69cDebugEnable parameter to the TR-069 client page (tr69cfg.cgi); the (6) timezone parameter to the Time and date page (sntpcfg.sntp); or the (7) hostname parameter in a save action to the Quick Stats page (psilan.cgi).  NOTE: this issue was SPLIT from CVE-2014-9020 per ADT1 due to different affected products and codebases.

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

## Which versions are affected by CVE-2014-9021?

It affects 1 product.


Products: Zteusa Zxdsl 831.

## How do I fix CVE-2014-9021?

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

## Is CVE-2014-9021 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9021 and fix it if it is affected.

What it is: CVE-2014-9021 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-9021 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-2014-9021/ (Markdown: https://insights.sbomify.com/CVE-2014-9021/index.md)
```

## Sources

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

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