# CVE-2023-48166: Path traversal in n/a

> Remote unauthenticated attackers can read arbitrary files via directory traversal in the SOAP server, potentially leading to system compromise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-xjjh-v77c-8mcm

## What is CVE-2023-48166?

CVE-2023-48166 is a high-severity path traversal vulnerability in n/a, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A directory traversal vulnerability in the SOAP Server integrated in Atos Unify OpenScape Voice V10 before V10R3.26.1 allows a remote attacker to view the contents of arbitrary files in the local file system. An unauthenticated attacker might obtain sensitive files that allow for the compromise of the underlying system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Unify Openscape Voice.

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

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

## Is CVE-2023-48166 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48166 is a high-severity path traversal vulnerability in n/a, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-48166 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-2023-48166/ (Markdown: https://insights.sbomify.com/CVE-2023-48166/index.md)
```

## Sources

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

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