# CVE-2017-8862: File upload in n/a

> An attacker can upload a malicious script via the web upgrade function to execute arbitrary code with root privileges on the device.

- **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:** 22 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r534-2r4v-gfqv

## What is CVE-2017-8862?

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

The webupgrade function on the Cohu 3960HD does not verify the firmware upgrade files or process, allowing an attacker to upload a specially crafted postinstall.sh file that will be executed with "root" privileges.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Cohuhd 3960hd Firmware.

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

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

## Is CVE-2017-8862 being exploited?

There is no known exploitation of CVE-2017-8862 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-8864](https://insights.sbomify.com/CVE-2017-8864/): Security feature bypass in n/a (critical 9.8)
- [CVE-2017-8863](https://insights.sbomify.com/CVE-2017-8863/): Information disclosure in n/a (high 7.5)
- [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-8862 and fix it if it is affected.

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

## Sources

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

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