# CVE-2023-22368: Privilege escalation in ELECOM Camera Assistant and QuickFileDealer

> Attackers can gain privileges via a Trojan horse DLL due to an untrusted search path in ELECOM Camera Assistant and QuickFileDealer.

- **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:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-p96j-jhf9-2vrr

## What is CVE-2023-22368?

CVE-2023-22368 is a high-severity vulnerability in ELECOM Camera Assistant and QuickFileDealer, published on 15 Feb 2023. 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

Untrusted search path vulnerability in ELECOM Camera Assistant 1.00 and QuickFileDealer Ver.1.2.1 and earlier allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2023-22368?

It affects 2 products.


Products: Elecom Camera Assistant, Elecom Quickfiledealer.

## How do I fix CVE-2023-22368?

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

## Is CVE-2023-22368 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22368 and fix it if it is affected.

What it is: CVE-2023-22368 is a high-severity vulnerability in ELECOM Camera Assistant and QuickFileDealer, published on 15 Feb 2023. 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-2023-22368 in the wild and no public exploit code.

Affected product: ELECOM Camera Assistant and QuickFileDealer. 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-2023-22368/ (Markdown: https://insights.sbomify.com/CVE-2023-22368/index.md)
```

## Sources

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

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