# CVE-2012-0016: Path traversal in n/a

> Local attackers can gain privileges by placing a malicious DLL in the working directory when a user opens a design 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:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vp5x-7793-46h5

## What is CVE-2012-0016?

CVE-2012-0016 is a critical path traversal vulnerability in n/a, published on 13 Mar 2012. 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 Expression Design; Expression Design SP1; and Expression Design 2, 3, and 4 allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a .xpr or .DESIGN file, aka "Expression Design Insecure Library Loading Vulnerability."

## Which versions are affected by CVE-2012-0016?

It affects 1 product.


Products: Microsoft Expression Design.

## How do I fix CVE-2012-0016?

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

## Is CVE-2012-0016 being exploited?

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

Public exploit code:

- Microsoft Internet Explorer - COALineDashStyleArray Unsafe Memory Access (MS12-022) (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0016 and fix it if it is affected.

What it is: CVE-2012-0016 is a critical path traversal vulnerability in n/a, published on 13 Mar 2012. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0016 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-2012-0016/ (Markdown: https://insights.sbomify.com/CVE-2012-0016/index.md)
```

## Sources

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

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