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

> Remote attackers can read or write arbitrary files on Fuji Xerox multifunction printers via crafted PJL commands.

- **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:** 7 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4gcj-jpgr-v4r6

## What is CVE-2018-16709?

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

### Official description

Fuji Xerox DocuCentre-V 3065, ApeosPort-VI C3371, ApeosPort-V C4475, ApeosPort-V C3375, DocuCentre-VI C2271, ApeosPort-V C5576, DocuCentre-IV C2263, DocuCentre-V C2263, and ApeosPort-V 5070 devices allow remote attackers to read or write to files via crafted PJL commands.

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

It affects 9 products.


Products: Fujixerox Apeosport-v 5070 Firmware, Fujixerox Apeosport-v C3375 Firmware, Fujixerox Apeosport-v C4475 Firmware, Fujixerox Apeosport-v C5576 Firmware, Fujixerox Apeosport-Vi C3371 Firmware, Fujixerox Docucentre-Iv C2263 Firmware, Fujixerox Docucentre-v 3065 Firmware, Fujixerox Docucentre-v C2263 Firmware, Fujixerox Docucentre-Vi C2271 Firmware.

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

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

## Is CVE-2018-16709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16709 is a critical path traversal vulnerability in n/a, published on 7 Sep 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-16709 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-16709/ (Markdown: https://insights.sbomify.com/CVE-2018-16709/index.md)
```

## Sources

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

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