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

> Local attackers can gain privileges by placing a malicious DLL in the current working directory of IBM Lotus Expeditor.

- **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:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wg8h-q3rc-9wvf

## What is CVE-2012-0187?

CVE-2012-0187 is a critical path traversal vulnerability in n/a, published on 22 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in IBM Lotus Expeditor 6.1.x and 6.2.x before 6.2 FP5+Security Pack allows local users to gain privileges via a Trojan horse DLL in the current working directory.

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

It affects 1 product.


Products: Ibm Lotus Expeditor.

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

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

## Is CVE-2012-0187 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0191](https://insights.sbomify.com/CVE-2012-0191/): Auth bypass in n/a (medium 5.0)
- [CVE-2012-0186](https://insights.sbomify.com/CVE-2012-0186/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0187 is a critical path traversal vulnerability in n/a, published on 22 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0187 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-2012-0187/ (Markdown: https://insights.sbomify.com/CVE-2012-0187/index.md)
```

## Sources

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

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