# CVE-2011-0107: Other in n/a

> Local attackers can execute arbitrary code and escalate privileges by placing a malicious DLL in the current working directory when a user opens a document.

- **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:** 13 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vf94-hmfp-f8r7

## What is CVE-2011-0107?

CVE-2011-0107 is a critical vulnerability in Microsoft Office, published on 13 Apr 2011. 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 Microsoft Office XP SP3, Office 2003 SP3, and Office 2007 SP2 allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a .docx file, aka "Office Component Insecure Library Loading Vulnerability."

## Which versions are affected by CVE-2011-0107?

It affects 1 product.


Products: Microsoft Office.

## How do I fix CVE-2011-0107?

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

## Is CVE-2011-0107 being exploited?

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

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0107 and fix it if it is affected.

What it is: CVE-2011-0107 is a critical vulnerability in Microsoft Office, published on 13 Apr 2011. 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-2011-0107 in the wild and no public exploit code.

Affected product: Microsoft Office. 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-2011-0107/ (Markdown: https://insights.sbomify.com/CVE-2011-0107/index.md)
```

## Sources

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

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