# CVE-2017-17105: Command injection in n/a

> Unauthenticated attackers can execute arbitrary commands on Zivif web cameras via blind command injection in CGI scripts.

- **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:** 18 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-whhw-3qj8-6jhm

## What is CVE-2017-17105?

CVE-2017-17105 is a critical command injection vulnerability in n/a, published on 18 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zivif PR115-204-P-RS V2.3.4.2103 and V4.7.4.2121 (and possibly in-between versions) web cameras are vulnerable to unauthenticated, blind remote command injection via CGI scripts used as part of the web interface, as demonstrated by a cgi-bin/iptest.cgi?cmd=iptest.cgi&-time="1504225666237"&-url=$(reboot) request.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Zivif Pr115-204-P-Rs Firmware.

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

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

## Is CVE-2017-17105 being exploited?

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

Public exploit code:

- Zivif Camera iptest.cgi Blind Remote Command Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2017-17106](https://insights.sbomify.com/CVE-2017-17106/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-17107](https://insights.sbomify.com/CVE-2017-17107/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17105 is a critical command injection vulnerability in n/a, published on 18 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17105 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-2017-17105/ (Markdown: https://insights.sbomify.com/CVE-2017-17105/index.md)
```

## Sources

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

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