# CVE-2007-0851: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a malformed UPX compressed executable due to a buffer overflow in the Trend Micro Scan Engine.

- **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 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h2w9-3qj3-7rf9

## What is CVE-2007-0851?

CVE-2007-0851 is a critical memory corruption vulnerability in n/a, published on 8 Feb 2007. 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

Buffer overflow in the Trend Micro Scan Engine 8.000 and 8.300 before virus pattern file 4.245.00, as used in other products such as Cyber Clean Center (CCC) Cleaner, allows remote attackers to execute arbitrary code via a malformed UPX compressed executable.

## Which versions are affected by CVE-2007-0851?

It affects 23 products.


Products: Trend Micro Client-Server-Messaging Suite Smb, Trend Micro Client-Server Suite Smb, Trend Micro Control Manager, Trend Micro Interscan Emanager, Trend Micro Interscan Messaging Security Suite, Trend Micro Interscan Viruswall, Trend Micro Interscan Viruswall for Windows Nt, Trend Micro Interscan Viruswall Scan Engine, Trend Micro Interscan Web Security Suite, Trend Micro Interscan Webmanager, Trend Micro Interscan Webprotect, Trend Micro Officescan, Trend Micro Pc-Cillin, Trend Micro Pc-Cillin Internet Security, Trend Micro Pc Cillin - Internet Security 2006, Trend Micro Portalprotect, Trend Micro Scanmail, Trend Micro Scanmail Emanager, Trend Micro Scanning Engine, Trend Micro Serverprotect and 3 more.

## How do I fix CVE-2007-0851?

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

## Is CVE-2007-0851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0533](https://insights.sbomify.com/CVE-2005-0533/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0851 and fix it if it is affected.

What it is: CVE-2007-0851 is a critical memory corruption vulnerability in n/a, published on 8 Feb 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-0851 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-2007-0851/ (Markdown: https://insights.sbomify.com/CVE-2007-0851/index.md)
```

## Sources

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

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