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

> Attackers can read arbitrary OS files via path traversal in the Maintenance Center web server, potentially leading to full device compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5x2r-g3pj-8qhq

## What is CVE-2018-7539?

CVE-2018-7539 is a critical path traversal vulnerability in n/a, published on 17 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Appear TV XC5000 and XC5100 devices with firmware 3.26.217, it is possible to read OS files with a specially crafted HTTP request (such as GET /../../../../../../../../../../../../etc/passwd) to the web server (fuzzd/0.1.1) running the Maintenance Center on port TCP/8088. This can lead to full compromise of the device.

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

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

It affects 2 products.


Products: Appeartv Xc5000 Firmware, Appeartv Xc5100 Firmware.

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

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

## Is CVE-2018-7539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7539 is a critical path traversal vulnerability in n/a, published on 17 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7539 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-7539/ (Markdown: https://insights.sbomify.com/CVE-2018-7539/index.md)
```

## Sources

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

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