# CVE-2018-14573: Path traversal in n/a

> Attackers can read arbitrary files via directory traversal in the Web Interface API of TightRope Media Carousel Digital Signage.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qxrx-v92j-rjvh

## What is CVE-2018-14573?

CVE-2018-14573 is a medium-severity path traversal vulnerability in n/a, published on 23 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Local File Inclusion (LFI) vulnerability exists in the Web Interface API of TightRope Media Carousel Digital Signage before 7.3.5. The RenderingFetch API allows for the downloading of arbitrary files through the use of directory traversal sequences, aka CSL-1683.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Trms Tightrope Media Carousel Digital Signage.

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

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

## Is CVE-2018-14573 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14573 is a medium-severity path traversal vulnerability in n/a, published on 23 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-14573 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-14573/ (Markdown: https://insights.sbomify.com/CVE-2018-14573/index.md)
```

## Sources

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

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