# CVE-2012-5378: Privilege escalation in n/a

> Local attackers can escalate privileges by placing a malicious DLL in a specific directory when ActiveTcl is installed in the root C drive.

- **Severity:** Medium 6.0 (`AV:L/AC:H/Au:S/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:** 11 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qqqh-jxq5-2j7v

## What is CVE-2012-5378?

CVE-2012-5378 is a medium-severity vulnerability in n/a, published on 11 Oct 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 the installation functionality in ActiveTcl 8.5.12, when installed in the top-level C:\ directory, allows local users to gain privileges via a Trojan horse DLL in the C:\TD\bin directory, which is added to the PATH system environment variable, as demonstrated by a Trojan horse wlbsctrl.dll file used by the "IKE and AuthIP IPsec Keying Modules" system service in Windows Vista SP1, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 Release Preview.

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

It affects 1 product.


Products: Activestate Activetcl.

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

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

## Is CVE-2012-5378 being exploited?

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

Public exploit code:

- IKE and AuthIP IPsec Keyring Modules Service (IKEEXT) - Missing DLL (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5378 is a medium-severity vulnerability in n/a, published on 11 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-5378 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-5378/ (Markdown: https://insights.sbomify.com/CVE-2012-5378/index.md)
```

## Sources

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

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