# CVE-2008-3878: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the Ultra Office Control ActiveX control, requiring user interaction.

- **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:** 2 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8vqq-hvqj-qc49

## What is CVE-2008-3878?

CVE-2008-3878 is a critical memory corruption vulnerability in n/a, published on 2 Sep 2008. 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

Stack-based buffer overflow in the Ultra.OfficeControl ActiveX control in OfficeCtrl.ocx 2.0.2008.801 in Ultra Shareware Ultra Office Control allows remote attackers to execute arbitrary code via long strUrl, strFile, and strPostData parameters to the HttpUpload method.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Ultrashareware Ultra Office Control.

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

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

## Is CVE-2008-3878 being exploited?

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

Public exploit code:

- Ultra Shareware Office Control - ActiveX Control Remote Buffer Overflow (exploitdb)
- Ultra Shareware Office Control ActiveX HttpUpload Buffer Overflow (metasploit)
- Ultra Shareware Office Control - ActiveX HttpUpload Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3879](https://insights.sbomify.com/CVE-2008-3879/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3878 is a critical memory corruption vulnerability in n/a, published on 2 Sep 2008. 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-3878 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-3878/ (Markdown: https://insights.sbomify.com/CVE-2008-3878/index.md)
```

## Sources

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

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