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

> Local attackers can gain privileges by placing a malicious DLL in the working directory of the Check Point Endpoint Security GUI.

- **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:** 19 Jun 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6p22-m9pj-g88j

## What is CVE-2012-2753?

CVE-2012-2753 is a medium-severity vulnerability in n/a, published on 19 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 TrGUI.exe in the Endpoint Connect (aka EPC) GUI in Check Point Endpoint Security R73.x and E80.x on the VPN blade platform, Endpoint Security VPN R75, Endpoint Connect R73.x, and Remote Access Clients E75.x allows local users to gain privileges via a Trojan horse DLL in the current working directory.

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

It affects 4 products.


Products: Checkpoint Endpoint Connect, Checkpoint Endpoint Security, Checkpoint Endpoint Security Vpn, Checkpoint Remote Access Clients.

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

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

## Is CVE-2012-2753 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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