# CVE-2009-3860: Path traversal in n/a

> Remote attackers can overwrite arbitrary files via insecure ActiveX methods in COMRaider, requiring specific Internet Explorer configurations.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **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:** 4 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fvf8-26gc-r75q

## What is CVE-2009-3860?

CVE-2009-3860 is a medium-severity path traversal vulnerability in n/a, published on 4 Nov 2009. 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

Multiple insecure method vulnerabilities in Idefense Labs COMRaider allow remote attackers to create or overwrite arbitrary files via the (1) CreateFolder and (2) Copy methods.  NOTE: this might only be a vulnerability in certain insecure configurations of Internet Explorer.

Weakness: CWE-264

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

It affects 1 product.


Products: Idefense Comraider.

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

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

## Is CVE-2009-3860 being exploited?

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

Public exploit code:

- iDefense COMRaider - ActiveX Control Multiple Insecure Method Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3860 is a medium-severity path traversal vulnerability in n/a, published on 4 Nov 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3860 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-3860/ (Markdown: https://insights.sbomify.com/CVE-2009-3860/index.md)
```

## Sources

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

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