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

> Attackers can exploit a path traversal vulnerability in ABUS TVIP devices to write arbitrary files and execute code with root privileges.

- **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:** 26 Oct 2023
- **Updated:** 11 Sep 2024
- **Also known as:** GHSA-2228-5m6x-4rqm

## What is CVE-2018-16739?

CVE-2018-16739 is a high-severity path traversal vulnerability in n/a, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on certain ABUS TVIP devices. Due to a path traversal in /opt/cgi/admin/filewrite, an attacker can write to files, and thus execute code arbitrarily with root privileges.

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

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

It affects 47 products.


Products: Abus Tvip 10000 Firmware, Abus Tvip 10001 Firmware, Abus Tvip 10005 Firmware, Abus Tvip 10005a Firmware, Abus Tvip 10005b Firmware, Abus Tvip 10050 Firmware, Abus Tvip 10051 Firmware, Abus Tvip 10055a Firmware, Abus Tvip 10055b Firmware, Abus Tvip 10500 Firmware, Abus Tvip 10550 Firmware, Abus Tvip 11000 Firmware, Abus Tvip 11050 Firmware, Abus Tvip 11500 Firmware, Abus Tvip 11501 Firmware, Abus Tvip 11502 Firmware, Abus Tvip 11550 Firmware, Abus Tvip 11551 Firmware, Abus Tvip 11552 Firmware, Abus Tvip 20000 Firmware and 27 more.

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

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

## Is CVE-2018-16739 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16739 exists.

## Other vulnerabilities in n/a

- [CVE-2018-17558](https://insights.sbomify.com/CVE-2018-17558/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-17878](https://insights.sbomify.com/CVE-2018-17878/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-17879](https://insights.sbomify.com/CVE-2018-17879/): Command injection in n/a (critical 9.8)
- [CVE-2018-17559](https://insights.sbomify.com/CVE-2018-17559/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16739 is a high-severity path traversal vulnerability in n/a, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16739 exists.

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-16739/ (Markdown: https://insights.sbomify.com/CVE-2018-16739/index.md)
```

## Sources

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

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