Vulnerability in Softing OPC UA C++ SDK (CVE-2023-29377)
Summary
Vulnerability in Softing OPC UA C++ SDK (CVE-2023-29377). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-29377 has been found in Softing OPC UA C++ SDK.
Successful exploitation can lead to full system takeover. CVSS score: 6.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Softing OPC UA C++ SDK CVE-2023-29377" on the vendor's site.
CVE-2023-29377 (Softing OPC UA C++ SDK) — CWE-23 / CVSS v3 6.6
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-23) exists in Softing OPC UA C++ SDK.
Check the vendor advisory for the affected versions of Softing OPC UA C++ SDK.
Severity: Medium (CVSS 6.6/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Softing OPC UA C++ SDK を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web industrial.softing.com
- web industrial.softing.com
- web cve@mitre.org
- web nvd.nist.gov
- web zerodayinitiative.com
- web github.com