# CVE-2017-16814: Path traversal in n/a

> Attackers can bypass local file restrictions in the Foxit MobilePDF iOS app via directory traversal during Wi-Fi transfers, potentially reading sensitive application files.

- **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:** 26 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r2c2-7v4f-hpfw

## What is CVE-2017-16814?

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

### Official description

A Directory Traversal issue was discovered in the Foxit MobilePDF app before 6.1 for iOS. This occurs by abusing the URL + escape character during a Wi-Fi transfer, which could be exploited by attackers to bypass intended restrictions on local application files.

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

## Which versions are affected by CVE-2017-16814?

It affects 1 product.


Products: Foxitsoftware Mobilepdf.

## How do I fix CVE-2017-16814?

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

## Is CVE-2017-16814 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16813](https://insights.sbomify.com/CVE-2017-16813/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16814 and fix it if it is affected.

What it is: CVE-2017-16814 is a medium-severity path traversal vulnerability in n/a, published on 26 Feb 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-2017-16814 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-2017-16814/ (Markdown: https://insights.sbomify.com/CVE-2017-16814/index.md)
```

## Sources

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

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