# CVE-2022-44725: Path traversal in n/a

> A local attacker can exploit a hard-coded file path in OPC Foundation LDS to load a malicious configuration file, leading to code execution with high privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-768r-2vmx-w6mf

## What is CVE-2022-44725?

CVE-2022-44725 is a high-severity path traversal vulnerability in n/a, published on 17 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OPC Foundation Local Discovery Server (LDS) through 1.04.403.478 uses a hard-coded file path to a configuration file. This allows a normal user to create a malicious file that is loaded by LDS (running as a high-privilege user).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Opcfoundation Local Discovery Server.

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

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

## Is CVE-2022-44725 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11672](https://insights.sbomify.com/CVE-2017-11672/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-17443](https://insights.sbomify.com/CVE-2017-17443/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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