# CVE-2017-12269: Cross-site scripting in Cisco Spark Messaging

> Authenticated attackers can inject malicious scripts into the Cisco Spark Messaging web UI, allowing them to execute code or steal sensitive user information.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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:** 5 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6mgp-v465-x83g

## What is CVE-2017-12269?

CVE-2017-12269 is a medium-severity cross-site scripting vulnerability in Cisco Spark Messaging, published on 5 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web UI of Cisco Spark Messaging Software could allow an authenticated, remote attacker to perform a stored cross-site scripting (XSS) attack. The vulnerability is due to insufficient input validation by the web UI of the affected software. An attacker could exploit this vulnerability by injecting XSS content into the web UI of the affected software. A successful exploit could allow the attacker to force a user to execute code of the attacker's choosing or allow the attacker to retrieve sensitive information from the user. Cisco Bug IDs: CSCvf70587, CSCvf70592.

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

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

It affects 1 product.


Products: Cisco Spark.

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

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

## Is CVE-2017-12269 being exploited?

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

## Other vulnerabilities in Cisco Spark Messaging

- [CVE-2016-1322](https://insights.sbomify.com/CVE-2016-1322/): Auth bypass in n/a (high 7.5)
- [CVE-2016-1324](https://insights.sbomify.com/CVE-2016-1324/): Denial of service in n/a (medium 5.3)
- [CVE-2016-1323](https://insights.sbomify.com/CVE-2016-1323/): Information disclosure in n/a (medium 4.3)
- [CVE-2015-6303](https://insights.sbomify.com/CVE-2015-6303/): Weak cryptography in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12269 is a medium-severity cross-site scripting vulnerability in Cisco Spark Messaging, published on 5 Oct 2017. 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-2017-12269 in the wild and no public exploit code.

Affected product: Cisco Spark Messaging. 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-12269/ (Markdown: https://insights.sbomify.com/CVE-2017-12269/index.md)
```

## Sources

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

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