# CVE-2007-0436: Privilege escalation in n/a

> Local users can gain LocalSystem privileges by exploiting a privilege drop failure in the X-Kryptor Secure Client's help command.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2mf4-723c-m9cr

## What is CVE-2007-0436?

CVE-2007-0436 is a medium-severity vulnerability in n/a, published on 4 Feb 2007. 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

Barron McCann X-Kryptor Driver BMS1446HRR (Xgntr BMS1351 Install BMS1472) in X-Kryptor Secure Client does not drop privileges when launching an Explorer window in response to a help command, which allows local users to gain LocalSystem privileges via interactive use of Explorer.

Weakness: CWE-264

## Which versions are affected by CVE-2007-0436?

It affects 4 products.


Products: Barron Mccann Install, Barron Mccann X-Kryptor Driver, Barron Mccann X-Kryptor Secure Client, Barron Mccann Xgntr.

## How do I fix CVE-2007-0436?

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

## Is CVE-2007-0436 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0436 and fix it if it is affected.

What it is: CVE-2007-0436 is a medium-severity vulnerability in n/a, published on 4 Feb 2007. 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: There is no known exploitation of CVE-2007-0436 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-2007-0436/ (Markdown: https://insights.sbomify.com/CVE-2007-0436/index.md)
```

## Sources

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

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