# CVE-2018-0145: Cross-site scripting in Cisco Data Center Analytics Framework

> Unauthenticated remote attackers can execute arbitrary scripts or access sensitive data via reflected XSS in the Cisco Data Center Analytics Framework web interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 22 Feb 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-rfcv-8275-47m6

## What is CVE-2018-0145?

CVE-2018-0145 is a medium-severity cross-site scripting vulnerability in Cisco Data Center Analytics Framework, published on 22 Feb 2018. 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

A vulnerability in the web-based management interface of the Cisco Data Center Analytics Framework application could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the interface of an affected system. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of the affected software. An attacker could exploit this vulnerability by persuading a user of the interface to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information on the affected system. Cisco Bug IDs: CSCvg45105.

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

## Which versions are affected by CVE-2018-0145?

It affects 1 product.


Products: Cisco Data Center Analytics Framework.

## How do I fix CVE-2018-0145?

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

## Is CVE-2018-0145 being exploited?

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

## Other vulnerabilities in Cisco Data Center Analytics Framework

- [CVE-2015-4189](https://insights.sbomify.com/CVE-2015-4189/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2019-16015](https://insights.sbomify.com/CVE-2019-16015/): Cisco Data Center Analytics Framework Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2018-0128](https://insights.sbomify.com/CVE-2018-0128/): Cross-site scripting in Cisco Data Center Analytics Framework (medium 6.1)
- [CVE-2018-0129](https://insights.sbomify.com/CVE-2018-0129/): Cross-site scripting in Cisco Data Center Analytics Framework (medium 6.1)
- [CVE-2018-0146](https://insights.sbomify.com/CVE-2018-0146/): Cross-site request forgery in Cisco Data Center Analytics Framework (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0145 and fix it if it is affected.

What it is: CVE-2018-0145 is a medium-severity cross-site scripting vulnerability in Cisco Data Center Analytics Framework, published on 22 Feb 2018. 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-2018-0145 in the wild and no public exploit code.

Affected product: Cisco Data Center Analytics Framework. 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-2018-0145/ (Markdown: https://insights.sbomify.com/CVE-2018-0145/index.md)
```

## Sources

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

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