# CVE-2008-7168: File upload in n/a

> Remote attackers can force arbitrary file downloads and overwrites via the UUSee UUUpgrade ActiveX control, potentially leading to code execution.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v98p-5p6g-589f

## What is CVE-2008-7168?

CVE-2008-7168 is a critical vulnerability in n/a, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Insecure method vulnerability in the UUSee UUUpgrade ActiveX control (UUUpgrade.ocx 3.0.2.12) allows remote attackers to force the download and overwrite of arbitrary files via crafted arguments to the Update method, as exploited in the wild in June 2009.

## Which versions are affected by CVE-2008-7168?

It affects 2 products.


Products: Uusee Uusee, Uusee Uuupgrade.ocx.

## How do I fix CVE-2008-7168?

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

## Is CVE-2008-7168 being exploited?

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

Public exploit code:

- UUSee 2008 - UUUpgrade ActiveX Control 'Update' Method Arbitrary File Download (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7168 and fix it if it is affected.

What it is: CVE-2008-7168 is a critical vulnerability in n/a, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7168 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-2008-7168/ (Markdown: https://insights.sbomify.com/CVE-2008-7168/index.md)
```

## Sources

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

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