# CVE-2010-3125: Path traversal in n/a

> Local attackers can execute arbitrary code via DLL hijacking by placing a malicious DLL in the same folder as a .tmx file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j7fw-hrf2-f7vm

## What is CVE-2010-3125?

CVE-2010-3125 is a critical path traversal vulnerability in n/a, published on 26 Aug 2010. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Untrusted search path vulnerability in TeamMate Audit Management Software Suite 8.0 patch 2 allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse mfc71enu.dll that is located in the same folder as a .tmx file.

## Which versions are affected by CVE-2010-3125?

It affects 1 product.


Products: Wolterskluwer Teammate Audit Management Software Suite.

## How do I fix CVE-2010-3125?

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

## Is CVE-2010-3125 being exploited?

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

Public exploit code:

- TeamMate Audit Management Software Suite - 'mfc71enu.dll' DLL Hijacking (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3125 and fix it if it is affected.

What it is: CVE-2010-3125 is a critical path traversal vulnerability in n/a, published on 26 Aug 2010. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-3125 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-2010-3125/ (Markdown: https://insights.sbomify.com/CVE-2010-3125/index.md)
```

## Sources

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

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