# CVE-2017-17106: Information disclosure in n/a

> Unauthenticated remote attackers can retrieve webcam credentials via a specific CGI request due to missing authentication checks.

- **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-r842-qg2m-qr63

## What is CVE-2017-17106?

CVE-2017-17106 is a critical 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

Credentials for Zivif PR115-204-P-RS V2.3.4.2103 Webcams can be obtained by an unauthenticated remote attacker using a standard web /cgi-bin/hi3510/param.cgi?cmd=getuser HTTP request. This vulnerability exists because of a lack of authentication checks in requests to CGI pages.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


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

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

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

## Is CVE-2017-17106 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17105](https://insights.sbomify.com/CVE-2017-17105/): Command injection 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-17106 and fix it if it is affected.

What it is: CVE-2017-17106 is a critical 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: There is no known exploitation of CVE-2017-17106 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-17106/ (Markdown: https://insights.sbomify.com/CVE-2017-17106/index.md)
```

## Sources

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

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