dbcve.org
Openscape VoiceApplication · Unify

CVE-2023-48166

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A directory traversal vulnerability exists in the SOAP Server component of Atos Unify OpenScape Voice V10 prior to version V10R3.26.1. An unauthenticated remote attacker can manipulate file path traversal sequences in SOAP requests to read arbitrary files from the local filesystem, potentially exposing configuration files, credentials, or other sensitive system data that could lead to complete system compromise.

MitigationUpgrade Atos Unify OpenScape Voice to version V10R3.26.1 or later to obtain the patch. If immediate patching is not feasible, restrict network access to the SOAP Server interface using firewall rules or network segmentation to limit exposure to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openscape VoiceApplication
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed OpenScape Voice version
    Check the system version through the administrative interface or by querying the system information via the management CLI or web interface. Look for a version string such as V10R3.x or V10.0.
    Affected if The installed version is V10.0 or any version prior to V10R3.26.1.
  2. Locate the SOAP Server component
    Review the system configuration to confirm the presence and location of the SOAP Server component. This is typically found in the server configuration files or management console.
    Affected if The SOAP Server component is present and running on the system.
  3. Verify SOAP Server network exposure
    Check the network bindings or firewall rules for the SOAP Server service. Determine if the SOAP interface is accessible from network endpoints, particularly untrusted networks.
    Affected if The SOAP Server is bound to a network-accessible IP and accepts external connections without restriction.
  4. Review SOAP request handling configuration
    Inspect the SOAP Server configuration files for path validation settings. Look for parameters controlling file path traversal or input sanitization in SOAP request processing.
    Affected if The SOAP Server lacks proper input validation or path traversal protection for file access requests.

The environment is affected if OpenScape Voice V10.0 or any version prior to V10R3.26.1 is installed with the SOAP Server component enabled and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Atos Unify OpenScape Voice to version V10R3.26.1 or later to obtain the patch. If immediate patching is not feasible, restrict network access to the SOAP Server interface using firewall rules or network segmentation to limit exposure to trusted sources only.

Recommended fix High confidence

V10R3.26.1

  1. 1. Back up the current OpenScape Voice configuration and database before initiating any upgrade.
  2. 2. Download the V10R3.26.1 or later release from the official Unify/Atos support portal (networks.unify.com or authorized distribution channels).
  3. 3. Review the upgrade guide for V10R3.26.1 to ensure all prerequisites are met, including compatible underlying software and hardware requirements.
  4. 4. Schedule a maintenance window as upgrades may require service downtime.
  5. 5. Execute the upgrade procedure following the official documentation for your specific deployment mode (standalone, clustered, etc.).
  6. 6. After upgrade completion, verify the SOAP Server service is running correctly.
  7. 7. Validate that the directory traversal vulnerability is resolved by attempting to access a test file outside the intended directory (or by confirming the fix through vendor release notes).
  8. 8. Monitor system logs for any anomalies and ensure all services are operational.
Caveat Review release notes for any configuration changes or deprecated features; patch releases typically maintain backward compatibility but require thorough testing in a staging environment first.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openscape Voice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48166 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data