# CVE-2019-12668: Cisco IOS and IOS XE Software Stored Banner Cross-Site Scripting Vulnerability

> Authenticated attackers can inject malicious scripts via the banner parameter in Cisco IOS XE web interfaces, potentially executing code or stealing data.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Sep 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-25j2-3m7q-pc9m

## What is CVE-2019-12668?

CVE-2019-12668 is a medium-severity cross-site scripting vulnerability in Cisco Ios, published on 25 Sep 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web framework code of Cisco IOS and Cisco IOS XE Software could allow an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the web interface of the affected software using the banner parameter. The vulnerability is due to insufficient input validation of the banner parameters that are passed to the web server of the affected software. An attacker could exploit this vulnerability by crafting a banner parameter and saving it. The attacker could then convince a user of the web interface to access a malicious link or could intercept a user request for the affected web interface and inject malicious code into the request. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected web interface or allow the attacker to access sensitive browser-based information.

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

## Which versions are affected by CVE-2019-12668?

It affects 2 products.


Products: Cisco Ios, Cisco Ios Xe.

## How do I fix CVE-2019-12668?

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

## Is CVE-2019-12668 being exploited?

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

## Other vulnerabilities in Cisco Ios

- [CVE-2017-12240](https://insights.sbomify.com/CVE-2017-12240/): Cisco IOS and IOS XE Software DHCP Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-3881](https://insights.sbomify.com/CVE-2017-3881/): Cisco IOS and IOS XE Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2018-0167](https://insights.sbomify.com/CVE-2018-0167/): Cisco IOS, XR, and XE Software Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2017-6736](https://insights.sbomify.com/CVE-2017-6736/): Cisco IOS and IOS XE Software SNMP Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-6737](https://insights.sbomify.com/CVE-2017-6737/): Cisco IOS and IOS XE Software SNMP Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12668 and fix it if it is affected.

What it is: CVE-2019-12668 is a medium-severity cross-site scripting vulnerability in Cisco Ios, published on 25 Sep 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12668 in the wild and no public exploit code.

Affected product: Cisco Ios. 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-2019-12668/ (Markdown: https://insights.sbomify.com/CVE-2019-12668/index.md)
```

## Sources

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

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