# CVE-2018-18930: File upload in n/a

> An authenticated attacker can upload a malicious ZIP file to achieve remote code execution on the digital signage server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p27c-8rq4-39cj

## What is CVE-2018-18930?

CVE-2018-18930 is a high-severity vulnerability in n/a, published on 29 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Tightrope Media Carousel digital signage product 7.0.4.104 contains an arbitrary file upload vulnerability in the Manage Bulletins/Upload feature, which can be leveraged to gain remote code execution. An authenticated attacker can upload a crafted ZIP file (based on an exported backup of existing "Bulletins") containing a malicious file. When uploaded, the system only checks for the presence of the needed files within the ZIP and, as long as the malicious file is named properly, will extract all contained files to a new directory on the system, named with a random GUID. The attacker can determine this GUID by previewing an image from the uploaded Bulletin within the web UI. Once the GUID is determined, the attacker can navigate to the malicious file and execute it. In testing, an ASPX web shell was uploaded, allowing for remote-code execution in the context of a restricted IIS user.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Trms Carousel Digital Signage.

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

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

## Is CVE-2018-18930 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18931](https://insights.sbomify.com/CVE-2018-18931/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18930 is a high-severity vulnerability in n/a, published on 29 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18930 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-2018-18930/ (Markdown: https://insights.sbomify.com/CVE-2018-18930/index.md)
```

## Sources

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

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