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

> Authenticated attackers can exploit a path traversal vulnerability in the OpenScape Voice Trace Manager user interface to access unauthorized files.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-vv28-qmp6-p32c

## What is CVE-2023-40264?

CVE-2023-40264 is a medium-severity path traversal vulnerability in n/a, published on 8 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Atos Unify OpenScape Voice Trace Manager V8 before V8 R0.9.11. It allows authenticated path traversal in the user interface.

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

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

It affects 1 product.


Products: Unify Openscape Voice Trace Manager.

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

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

## Is CVE-2023-40264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-40263](https://insights.sbomify.com/CVE-2023-40263/): Command injection in n/a (high 8.8)
- [CVE-2023-40262](https://insights.sbomify.com/CVE-2023-40262/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40264 is a medium-severity path traversal vulnerability in n/a, published on 8 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-40264 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-40264/ (Markdown: https://insights.sbomify.com/CVE-2023-40264/index.md)
```

## Sources

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

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