# CVE-2023-29377: Path traversal in Secure Integration Server

> Attackers can bypass directory path restrictions in Softing OPC UA SDK and Secure Integration Server to access or modify unauthorized files.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-hwrv-x7wv-x58q

## What is CVE-2023-29377?

CVE-2023-29377 is a medium-severity path traversal vulnerability in Softing Secure Integration Server, published on 14 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Softing OPC UA C++ SDK through 6.20 and Softing Secure Integration Server through 1.22. By using FileType renames, it is possible to bypass limitations on assignment of a directory path to FileDirectory OPC UA objects and a file path to File OPC UA objects.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2023-29377 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29377 is a medium-severity path traversal vulnerability in Softing Secure Integration Server, published on 14 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29377 in the wild and no public exploit code.

Affected product: Softing Secure Integration Server. 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-29377/ (Markdown: https://insights.sbomify.com/CVE-2023-29377/index.md)
```

## Sources

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

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