# CVE-2020-11949: Path traversal in n/a

> An authenticated attacker can exploit a path traversal vulnerability in the web service to read arbitrary files from the camera's local filesystem.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5q49-56vw-8vr6

## What is CVE-2020-11949?

CVE-2020-11949 is a medium-severity path traversal vulnerability in n/a, published on 28 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

testserver.cgi of the web service on VIVOTEK Network Cameras before XXXXX-VVTK-2.2002.xx.01x (and before XXXXX-VVTK-0XXXX_Beta2) allows an authenticated user to obtain arbitrary files from a camera's local filesystem. For example, this affects IT9388-HT devices.

## Which versions are affected by CVE-2020-11949?

It affects 194 products.


Products: Vivotek Cc8160\(hs\) Firmware, Vivotek Cc8160 Firmware, Vivotek Cc8370-Hv Firmware, Vivotek Cc8371-Hv Firmware, Vivotek Cc9381-Hv Firmware, Vivotek Cd8371-Hntv Firmware, Vivotek Cd8371-Hnvf2 Firmware, Vivotek Fd8166a-N Firmware, Vivotek Fd8166a Firmware, Vivotek Fd8167a Firmware, Vivotek Fd8169a Firmware, Vivotek Fd816b-Hf2 Firmware, Vivotek Fd816b-Ht Firmware, Vivotek Fd816ba-Hf2 Firmware, Vivotek Fd816ba-Ht Firmware, Vivotek Fd816c-Hf2 Firmware, Vivotek Fd816ca-Hf2 Firmware, Vivotek Fd8177-H Firmware, Vivotek Fd8177-Ht Firmware, Vivotek Fd8179-H Firmware and 174 more.

## How do I fix CVE-2020-11949?

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

## Is CVE-2020-11949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11950](https://insights.sbomify.com/CVE-2020-11950/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11949 and fix it if it is affected.

What it is: CVE-2020-11949 is a medium-severity path traversal vulnerability in n/a, published on 28 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11949 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-2020-11949/ (Markdown: https://insights.sbomify.com/CVE-2020-11949/index.md)
```

## Sources

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

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