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

> An attacker can view sensitive application logic and source code on the Cohu 3960 device via a web browser.

- **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:** 22 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-42xr-w96f-53vq

## What is CVE-2017-8863?

CVE-2017-8863 is a high-severity vulnerability in n/a, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information disclosure of .esp source code on the Cohu 3960 allows an attacker to view sensitive information such as application logic with a simple web browser.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cohuhd 3960hd Firmware.

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

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

## Is CVE-2017-8863 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8861](https://insights.sbomify.com/CVE-2017-8861/): Missing authorization in n/a (critical 9.8)
- [CVE-2017-8862](https://insights.sbomify.com/CVE-2017-8862/): File upload in n/a (critical 9.8)
- [CVE-2017-8864](https://insights.sbomify.com/CVE-2017-8864/): Security feature bypass in n/a (critical 9.8)
- [CVE-2017-8860](https://insights.sbomify.com/CVE-2017-8860/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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