# CVE-2010-3190: Other in n/a

> Local attackers can gain privileges or execute code by placing a malicious DLL in the working directory of MFC applications.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 31 Aug 2010
- **Updated:** 28 May 2026
- **Also known as:** GHSA-4qmw-vcgw-w2vh

## What is CVE-2010-3190?

CVE-2010-3190 is a high-severity vulnerability in Apple Itunes, published on 31 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 the Microsoft Foundation Class (MFC) Library in Microsoft Visual Studio .NET 2003 SP1; Visual Studio 2005 SP1, 2008 SP1, and 2010; Visual C++ 2005 SP1, 2008 SP1, and 2010; and Exchange Server 2010 Service Pack 3, 2013, and 2013 allows local users to gain privileges via a Trojan horse dwmapi.dll file in the current working directory during execution of an MFC application such as AtlTraceTool8.exe (aka ATL MFC Trace Tool), as demonstrated by a directory that contains a TRC, cur, rs, rct, or res file, aka "MFC Insecure Library Loading Vulnerability."

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 4 products.


Products: Apple Itunes, Microsoft Visual C\+\+, Microsoft Visual Studio, Microsoft Visual Studio .Net.

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

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

## Is CVE-2010-3190 being exploited?

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

## Other vulnerabilities in Apple Itunes

- [CVE-2010-1763](https://insights.sbomify.com/CVE-2010-1763/): Other in n/a (critical 10.0)
- [CVE-2010-1769](https://insights.sbomify.com/CVE-2010-1769/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1035](https://insights.sbomify.com/CVE-2013-1035/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-0677](https://insights.sbomify.com/CVE-2012-0677/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-3219](https://insights.sbomify.com/CVE-2011-3219/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3190 is a high-severity vulnerability in Apple Itunes, published on 31 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-3190 in the wild and no public exploit code.

Affected product: Apple Itunes. 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-3190/ (Markdown: https://insights.sbomify.com/CVE-2010-3190/index.md)
```

## Sources

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

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