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

> Local attackers can gain privileges by placing malicious DLLs in the current working directory when opening specific Groove files.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vqfc-8pxq-vr5h

## What is CVE-2010-3146?

CVE-2010-3146 is a critical path traversal vulnerability in n/a, published on 27 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

Multiple untrusted search path vulnerabilities in Microsoft Groove 2007 SP2 allow local users to gain privileges via a Trojan horse (1) mso.dll or (2) GroovePerfmon.dll file in the current working directory, as demonstrated by a directory that contains a Groove vCard (.vcg) or Groove Tool Archive (.gta) file, aka "Microsoft Groove Insecure Library Loading Vulnerability."

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

It affects 1 product.


Products: Microsoft Groove.

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

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

## Is CVE-2010-3146 being exploited?

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

Public exploit code:

- Microsoft Office Groove 2007 - 'mso.dll' DLL Hijacking (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3146 is a critical path traversal vulnerability in n/a, published on 27 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-3146 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-3146/ (Markdown: https://insights.sbomify.com/CVE-2010-3146/index.md)
```

## Sources

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

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