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

> Remote attackers can read arbitrary files on VIVOTEK network cameras via path traversal in the admin download service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wq34-m4x9-8pmg

## What is CVE-2017-9829?

CVE-2017-9829 is a high-severity path traversal vulnerability in n/a, published on 23 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

'/cgi-bin/admin/downloadMedias.cgi' of the web service in most of the VIVOTEK Network Cameras is vulnerable, which allows remote attackers to read any file on the camera's Linux filesystem via a crafted HTTP request containing ".." sequences. This vulnerability is already verified on VIVOTEK Network Camera IB8369/FD8164/FD816BA; most others have similar firmware that may be affected.

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

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

It affects 3 products.


Products: Vivotek Network Camera Fd8164 Firmware, Vivotek Network Camera Fd816ba Firmware, Vivotek Network Camera Ib8369 Firmware.

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

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

## Is CVE-2017-9829 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9828](https://insights.sbomify.com/CVE-2017-9828/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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