# CVE-2008-2439: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the OfficeScanNT Listener service, exposing sensitive data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6cc4-g986-cx7v

## What is CVE-2008-2439?

CVE-2008-2439 is a medium-severity path traversal vulnerability in n/a, published on 3 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the UpdateAgent function in TmListen.exe in the OfficeScanNT Listener service in the client in Trend Micro OfficeScan 7.3 Patch 4 build 1367 and other builds before 1372, OfficeScan 8.0 SP1 before build 1222, OfficeScan 8.0 SP1 Patch 1 before build 3087, and Worry-Free Business Security 5.0 before build 1220 allows remote attackers to read arbitrary files via directory traversal sequences in an HTTP request.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Trend Micro Officescan, Trend Micro Worry Free Business Security.

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

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

## Is CVE-2008-2439 being exploited?

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

Public exploit code:

- TrendMicro OfficeScanNT Listener Traversal Arbitrary File Access (metasploit)

## Other vulnerabilities in n/a

- [CVE-2008-3862](https://insights.sbomify.com/CVE-2008-3862/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-4402](https://insights.sbomify.com/CVE-2008-4402/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-3454](https://insights.sbomify.com/CVE-2007-3454/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-3455](https://insights.sbomify.com/CVE-2007-3455/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-1381](https://insights.sbomify.com/CVE-2006-1381/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2439 is a medium-severity path traversal vulnerability in n/a, published on 3 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2439 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-2439/ (Markdown: https://insights.sbomify.com/CVE-2008-2439/index.md)
```

## Sources

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

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