dbcve.org
Unify Openscape 4000Application · Atos

CVE-2023-29475

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
inventory in Atos Unify OpenScape 4000 Platform and OpenScape 4000 Manager Platform 10 R1 before 10 R1.34.4 allows an unauthenticated attacker to run arbitrary commands on the platform operating system and achieve administrative access, aka OSFOURK-23543.

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

The inventory component in Atos Unify OpenScape 4000 Platform and Manager Platform versions prior to 10 R1.34.4 contains a critical authentication bypass vulnerability. An unauthenticated remote attacker can inject and execute arbitrary operating system commands through the inventory feature, directly escalating to administrative privileges on the affected platform.

MitigationUpgrade to OpenScape 4000 version 10 R1.34.4 or later. If immediate patching is not possible, restrict network access to the inventory management interface using firewall rules or network segmentation, as the vulnerability is exploitable without any credentials.

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
Unify Openscape 4000Application
Affected:= 10
Unify Openscape 4000 ManagerApplication
Affected:= 10

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
High
Availability
High

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

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 4000 version
    Access the system administration interface or check the version information in the system management console. The version typically displays as '10' followed by a revision number such as R1.x.y.
    Affected if The installed version is OpenScape 4000 version 10 with a revision earlier than R1.34.4 (for example, R1.34.0 through R1.34.3).
  2. Confirm the product variant
    Determine whether the installation is OpenScape 4000 Platform or OpenScape 4000 Manager Platform by reviewing the system information or license details in the management console.
    Affected if Either the base Platform or Manager Platform variant is present and meets the version condition in step 1.
  3. Check network accessibility of the inventory interface
    Verify if TCP ports used by the inventory management component are reachable from untrusted networks. The inventory feature typically listens on management ports accessible via web interface.
    Affected if The inventory management interface is exposed to network segments that contain untrusted or internet-facing systems.
  4. Verify if inventory feature is enabled
    Review the system configuration to confirm whether the inventory component is activated. This can be checked through the admin console under system services or component status.
    Affected if The inventory feature is enabled and running on a version that is prior to R1.34.4.

A system is affected if it runs OpenScape 4000 or OpenScape 4000 Manager version 10 with a revision prior to R1.34.4 and has the inventory component exposed or enabled.

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 to OpenScape 4000 version 10 R1.34.4 or later. If immediate patching is not possible, restrict network access to the inventory management interface using firewall rules or network segmentation, as the vulnerability is exploitable without any credentials.

Recommended fix High confidence

10 R1.34.4 (or any later stable release)

  1. 1. Identify the current version of Unify Openscape 4000 or Unify Openscape 4000 Manager by accessing the system administration interface or checking the system information.
  2. 2. Confirm the installed version is 10 R1 prior to version 10 R1.34.4, as versions before this patch are vulnerable.
  3. 3. Create a full backup of the system configuration and data according to the vendor's backup procedures to ensure business continuity.
  4. 4. Obtain the fixed version (10 R1.34.4 or later) from the official Unify/Atos support channels at networks.unify.com or through your authorized support representative.
  5. 5. Follow the official upgrade instructions provided in the Unify Openscape 4000 documentation to apply the version 10 R1.34.4 update.
  6. 6. After upgrade completion, verify the system version reflects 10 R1.34.4 or later and confirm normal system operation.
  7. 7. Validate that the command injection vulnerability is resolved by reviewing system logs and ensuring no unauthorized access attempts occur.
Caveat Review release notes for 10 R1.34.4 to check for any configuration changes or feature modifications that may require adjustment during the upgrade process.

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

Fix this in Unify Openscape 4000 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29475 — 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-29475 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