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

> Local attackers can escalate privileges by placing a malicious DLL in the current working directory of the Cisco VPN Client.

- **Severity:** Medium 6.9 (`AV:L/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:** 16 Sep 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2767-v9j6-723w

## What is CVE-2012-3052?

CVE-2012-3052 is a medium-severity vulnerability in n/a, published on 16 Sep 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 Cisco VPN Client 5.0 allows local users to gain privileges via a Trojan horse DLL in the current working directory, aka Bug ID CSCua28747.

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

It affects 1 product.


Products: Cisco Vpn Client.

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

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

## Is CVE-2012-3052 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1106](https://insights.sbomify.com/CVE-2002-1106/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-1107](https://insights.sbomify.com/CVE-2002-1107/): Weak cryptography in n/a (high 7.5)
- [CVE-2015-7600](https://insights.sbomify.com/CVE-2015-7600/): Privilege escalation in n/a (high 7.2)
- [CVE-2006-2679](https://insights.sbomify.com/CVE-2006-2679/): Privilege escalation in n/a (high 7.2)
- [CVE-2002-1447](https://insights.sbomify.com/CVE-2002-1447/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3052 is a medium-severity vulnerability in n/a, published on 16 Sep 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-3052 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-3052/ (Markdown: https://insights.sbomify.com/CVE-2012-3052/index.md)
```

## Sources

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

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