CVE-2023-29473
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 · uneditedwebservice 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-23710.
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 confidenceThis is a critical command injection vulnerability in the webservice component of Atos Unify OpenScape 4000 Platform and Manager Platform. An unauthenticated attacker can exploit this flaw to execute arbitrary operating system commands and gain administrative privileges on the affected system.
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= 10= 10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenScape 4000 versionAccess the system management interface or check the installed software version via command line or system information panel. Look for the exact version string such as V10, V10 R1.x, or similar version notation.Affected if The installed version is 10.x (any subversion of 10) without having applied the R1.34.4 patch.
-
Confirm webservice component is runningCheck the system services or process list for the webservice component. On the management platform, navigate to system status or services configuration to verify the webservice is active.Affected if The webservice component is enabled and running - this is the vulnerable component that must be active for exploitation.
-
Determine webservice network accessibilityReview firewall rules, network configuration, or access control lists to determine if the webservice interface (typically ports 80/443 or vendor-specified ports) is accessible from untrusted networks.Affected if The webservice is exposed to untrusted or public networks without proper access restrictions - the flaw is remotely exploitable by unauthenticated attackers.
-
Check patch level of webserviceIf accessible, examine the webservice component version or patch information through the management interface, or review applied patches in the system update history.Affected if The installed patch level is earlier than R1.34.4, indicating the command injection vulnerability remains unfixed.
A user is affected if their OpenScape 4000 or Manager version is 10.x, the webservice component is enabled, and the patch level is below R1.34.4, especially if the interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor patch 10 R1.34.4 or later to the OpenScape 4000 webservice component. If patching is immediately infeasible, restrict network access to the webservice interface via firewall rules or disable remote access until the patch can be deployed.
10 R1.34.4 (or later stable release)
- 1. Identify the current installed version of Unify Openscape 4000 or Openscape 4000 Manager by accessing the system administration interface or running version diagnostics
- 2. Confirm the current version is below 10 R1.34.4 (versions 10 R1 through 10 R1.34.3 are affected)
- 3. Review the official Unify release notes and upgrade documentation for version 10 R1.34.4
- 4. Schedule a maintenance window and create a full system backup
- 5. Download the 10 R1.34.4 (or latest stable) update package from the official Unify support portal at networks.unify.com
- 6. Apply the upgrade following Unify's documented upgrade procedure for Openscape 4000 platform
- 7. After upgrade completion, verify the system version reflects 10 R1.34.4 or later
- 8. Test that the webservice is functioning normally and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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