# CVE-2007-0856: Privilege escalation in n/a

> Local attackers can exploit insecure device permissions to execute arbitrary code in kernel context, leading to privilege escalation.

- **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:** 8 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8whq-qmmg-8jxf

## What is CVE-2007-0856?

CVE-2007-0856 is a high-severity vulnerability in n/a, published on 8 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TmComm.sys 1.5.0.1052 in the Trend Micro Anti-Rootkit Common Module (RCM), with the VsapiNI.sys 3.320.0.1003 scan engine, as used in Trend Micro PC-cillin Internet Security 2007, Antivirus 2007, Anti-Spyware for SMB 3.2 SP1, Anti-Spyware for Consumer 3.5, Anti-Spyware for Enterprise 3.0 SP2, Client / Server / Messaging Security for SMB 3.5, Damage Cleanup Services 3.2, and possibly other products, assigns Everyone write permission for the \\.\TmComm DOS device interface, which allows local users to access privileged IOCTLs and execute arbitrary code or overwrite arbitrary memory in the kernel context.

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

It affects 8 products.


Products: Trend Micro Client-Server-Messaging Security, Trend Micro Damage Cleanup Services, Trend Micro Pc-Cillin Internet Security, Trend Micro Tmcomm.sys, Trend Micro Trend Micro Antirootkit Common Module, Trend Micro Trend Micro Antispyware, Trend Micro Trend Micro Antivirus, Trend Micro Vsapini.sys.

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

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

## Is CVE-2007-0856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2437](https://insights.sbomify.com/CVE-2008-2437/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0325](https://insights.sbomify.com/CVE-2007-0325/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0856 is a high-severity vulnerability in n/a, published on 8 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0856 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-0856/ (Markdown: https://insights.sbomify.com/CVE-2007-0856/index.md)
```

## Sources

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

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