# CVE-2018-9081: Iomega and LenovoEMC NAS Web UI Vulnerabilities

> Attackers can inject scripts via malicious filenames in NAS Content Viewer, potentially leading to code execution or account takeover when users interact with the files.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:N/AC:H/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:** 28 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m3g4-7856-hf77

## What is CVE-2018-9081?

CVE-2018-9081 is a medium-severity cross-site scripting vulnerability in Lenovo Group LTD EZ Media and Backup Center, published on 28 Sep 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

For some Iomega, Lenovo, LenovoEMC NAS devices versions 4.1.402.34662 and earlier, the file name used for assets accessible through the Content Viewer application are vulnerable to self cross-site scripting self-XSS. As a result, adversaries can add files to shares accessible from the Content Viewer with a cross site scripting payload in its name, and wait for a user to try and rename the file for their payload to trigger.

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

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

It affects 20 products.


Products: Lenovo Ez Media \& Backup Center Firmware, Lenovo Ix2 Firmware, Lenovo Ix4-300d Firmware, Lenovo Px12-400r Firmware, Lenovo Px12-450r Firmware, Lenovo Px2-300d Firmware, Lenovo Px4-300d Firmware, Lenovo Px4-300r Firmware, Lenovo Px4-400d Firmware, Lenovo Px4-400r Firmware, Lenovo Px6-300d Firmware, Lenovo Storcenter Ix2-Dl Firmware, Lenovo Storcenter Ix2 Firmware, Lenovo Storcenter Ix4-300d Firmware, Lenovo Storcenter Px12-400r Firmware, Lenovo Storcenter Px12-450r Firmware, Lenovo Storcenter Px2-300d Firmware, Lenovo Storcenter Px4-300d Firmware, Lenovo Storcenter Px4-300r Firmware, Lenovo Storcenter Px6-300d Firmware.

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

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

## Is CVE-2018-9081 being exploited?

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

## Other vulnerabilities in Lenovo Group LTD EZ Media and Backup Center

- [CVE-2018-9079](https://insights.sbomify.com/CVE-2018-9079/): Iomega and LenovoEMC NAS Web UI Vulnerabilities (critical 9.8)
- [CVE-2018-9078](https://insights.sbomify.com/CVE-2018-9078/): Iomega and LenovoEMC NAS Web UI Vulnerabilities (high 8.8)
- [CVE-2018-9082](https://insights.sbomify.com/CVE-2018-9082/): Iomega and LenovoEMC NAS Web UI Vulnerabilities (high 8.8)
- [CVE-2018-9080](https://insights.sbomify.com/CVE-2018-9080/): Iomega and LenovoEMC NAS Web UI Vulnerabilities (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9081 is a medium-severity cross-site scripting vulnerability in Lenovo Group LTD EZ Media and Backup Center, published on 28 Sep 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-9081 in the wild and no public exploit code.

Affected product: Lenovo Group LTD EZ Media and Backup Center. 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-9081/ (Markdown: https://insights.sbomify.com/CVE-2018-9081/index.md)
```

## Sources

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

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