# CVE-2022-36415: Privilege escalation in n/a

> A DLL hijacking vulnerability in the Beyond Compare uninstaller allows local attackers to execute arbitrary code with SYSTEM privileges by placing malicious DLLs in the Windows Temp folder.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jvp2-xqw5-43j5

## What is CVE-2022-36415?

CVE-2022-36415 is a high-severity vulnerability in n/a, published on 23 Jul 2022. 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

A DLL hijacking vulnerability exists in the uninstaller in Scooter Beyond Compare 1.8a through 4.4.2 before 4.4.3 when installed via the EXE installer. The uninstaller attempts to load DLLs out of a Windows Temp folder. If a standard user places malicious DLLs in the C:\Windows\Temp\ folder, and then the uninstaller is run as SYSTEM, the DLLs will execute with elevated privileges.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2022-36415?

It affects 1 product.


Products: Scootersoftware Beyond Compare.

## How do I fix CVE-2022-36415?

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

## Is CVE-2022-36415 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36414](https://insights.sbomify.com/CVE-2022-36414/): Privilege escalation in n/a (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36415 and fix it if it is affected.

What it is: CVE-2022-36415 is a high-severity vulnerability in n/a, published on 23 Jul 2022. 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-2022-36415 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-2022-36415/ (Markdown: https://insights.sbomify.com/CVE-2022-36415/index.md)
```

## Sources

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

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