# CVE-2008-2434: Code injection in n/a

> Remote attackers can execute arbitrary code by tricking users into visiting a malicious site that exploits the Trend Micro HouseCall ActiveX control.

- **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:** 23 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2frg-p6rf-fcfj

## What is CVE-2008-2434?

CVE-2008-2434 is a critical code injection vulnerability in n/a, published on 23 Dec 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

The Trend Micro HouseCall ActiveX control 6.51.0.1028 and 6.6.0.1278 in Housecall_ActiveX.dll allows remote attackers to download an arbitrary library file onto a client system via a "custom update server" argument.  NOTE: this can be leveraged for code execution by writing to a Startup folder.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Trend Micro Housecall.

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

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

## Is CVE-2008-2434 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2435](https://insights.sbomify.com/CVE-2008-2435/): Use after free in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2434 is a critical code injection vulnerability in n/a, published on 23 Dec 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: There is no known exploitation of CVE-2008-2434 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-2008-2434/ (Markdown: https://insights.sbomify.com/CVE-2008-2434/index.md)
```

## Sources

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

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