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

> Remote attackers can inject arbitrary web script or HTML into the Airties Air 6372 modem interface via the productboardtype parameter.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 13 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pxc7-qwq2-vp9j

## What is CVE-2014-100032?

CVE-2014-100032 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Jan 2015. 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 top.html in the Airties Air 6372 modem allows remote attackers to inject arbitrary web script or HTML via the productboardtype parameter.

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

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

It affects 1 product.


Products: Airties Air 6372.

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

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

## Is CVE-2014-100032 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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