# CVE-2009-0686: Privilege escalation in n/a

> Local attackers can escalate privileges by sending a crafted IOCTL request to the Trend Micro Activity Monitor Module, overwriting memory.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gfhg-7w8w-j26f

## What is CVE-2009-0686?

CVE-2009-0686 is a high-severity vulnerability in n/a, published on 1 Apr 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The TrendMicro Activity Monitor Module (tmactmon.sys) 2.52.0.1002 in Trend Micro Internet Pro 2008 and 2009, and Security Pro 2008 and 2009, allows local users to gain privileges via a crafted IRP in a METHOD_NEITHER IOCTL request to \Device\tmactmon that overwrites memory.

Weakness: CWE-399

## Which versions are affected by CVE-2009-0686?

It affects 1 product.


Products: Trendmicro Internet Security.

## How do I fix CVE-2009-0686?

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

## Is CVE-2009-0686 being exploited?

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

Public exploit code:

- Trend Micro Internet Security Pro 2009 - Priviliege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-3189](https://insights.sbomify.com/CVE-2010-3189/): Code injection in n/a (critical 9.3)
- [CVE-2016-1225](https://insights.sbomify.com/CVE-2016-1225/): Information disclosure in n/a (medium 6.5)
- [CVE-2016-1226](https://insights.sbomify.com/CVE-2016-1226/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0686 and fix it if it is affected.

What it is: CVE-2009-0686 is a high-severity vulnerability in n/a, published on 1 Apr 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0686 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-2009-0686/ (Markdown: https://insights.sbomify.com/CVE-2009-0686/index.md)
```

## Sources

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

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