dbcve.org
Unify Openscape 4000Application · Atos

CVE-2023-29474

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-23552.

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 OpenScape 4000 Platform contains a command injection vulnerability in its inventory management functionality. An unauthenticated attacker can send specially crafted requests to the inventory feature, causing arbitrary OS command execution and achieving full administrative access to the platform.

MitigationUpgrade to OpenScape 4000 version 10 R1.34.4 or later. Given the critical severity (CVSS 9.8) and unauthenticated nature, this vulnerability should be prioritized for immediate remediation.

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 OpenScape 4000 installation
    Check system inventory, running services, or product documentation for OpenScape 4000 or OpenScape 4000 Manager presence. Look for processes named 'OpenScape 4000' or related services on the system.
    Affected if OpenScape 4000 or OpenScape 4000 Manager software is installed on the system
  2. Determine installed version
    Locate the version information for the OpenScape 4000 installation. This is typically found in the product's about page, system information, or configuration files. Compare the version number to the affected range (version 10).
    Affected if The installed version is OpenScape 4000 version 10 (any subversion)
  3. Verify inventory management feature
    Check if the inventory management functionality is accessible. This may involve reviewing the web interface, API endpoints, or service documentation for the inventory feature. Look for endpoints or modules related to inventory management.
    Affected if The inventory management feature is enabled and accessible on the system
  4. Assess network exposure
    Determine if the inventory management interface is exposed to network access. Check firewall rules, service bindings (listen addresses), and access control lists. Identify whether the service is reachable from untrusted networks.
    Affected if The inventory management interface is reachable from unauthenticated network connections (especially external/untrusted networks)

If OpenScape 4000 version 10 with the inventory management feature is exposed to the network, the system is likely vulnerable to unauthenticated command injection via CVE-2023-29474.

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. Given the critical severity (CVSS 9.8) and unauthenticated nature, this vulnerability should be prioritized for immediate remediation.

Recommended fix Moderate confidence

10 R1.34.4 or later

  1. Identify the current installed version of Unify Openscape 4000 or Openscape 4000 Manager
  2. Access the official Unify support portal at networks.unify.com to obtain the version 10 R1.34.4 or later patch
  3. Review the upgrade documentation and release notes for version 10 R1.34.4
  4. Schedule a maintenance window for the upgrade process
  5. Perform a complete backup of the current system configuration
  6. Apply the upgrade to version 10 R1.34.4 or later following the official upgrade procedure
  7. Verify the upgrade was successful and the system is operational
  8. Confirm the vulnerability is resolved by checking the system version

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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