Unify Openscape 4000 AssistantApplication · Atos

CVE-2023-35032

HIGH · 8.8 CVSS v3.1 Published 2023-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Atos Unify OpenScape 4000 Assistant V10 R1 before V10 R1.42.0 and V10 R1.34.8 and Manager V10 R1 before V10 R1.42.0 and V10 R1.34.8 allow command injection by authenticated users, aka OSFOURK-23554.

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

Atos Unify OpenScape 4000 Assistant and Manager V10 R1 contain a command injection vulnerability allowing authenticated users to execute arbitrary commands on the underlying system. The vulnerability exists in versions prior to V10 R1.42.0 and V10 R1.34.8, likely due to insufficient input validation when processing user-supplied data in system management functions.

MitigationUpgrade Atos Unify OpenScape 4000 Assistant and Manager to version V10 R1.42.0 or V10 R1.34.8 or later. If immediate patching is not possible, restrict network access to management interfaces to trusted IPs and monitor for suspicious command execution patterns.

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 4000 AssistantApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 if Atos Unify OpenScape 4000 is installed
    Locate the installation directory or check system inventory for Atos Unify Openscape 4000 Assistant or Manager software
    Affected if Either product is present on the system
  2. Determine the installed version
    Check the version of the installed OpenScape 4000 Assistant or Manager - typically accessible via the application GUI, about page, or installation logs
    Affected if Version is displayed as V10 R1 but not R1.42.0 or R1.34.8 or later
  3. Compare version against vulnerable ranges
    Review the version number against the affected ranges: versions prior to V10 R1.42.0 and V10 R1.34.8 are vulnerable
    Affected if Installed version is earlier than V10 R1.34.8 or is between V10 R1.34.8 and V10 R1.42.0 (exclusive)
  4. Verify if management interface is network-accessible
    Check if the OpenScape 4000 management interface ports are exposed to network access beyond trusted internal networks
    Affected if Management interface is reachable from untrusted networks

User is affected if Atos Unify OpenScape 4000 Assistant or Manager V10 R1 is installed with a version prior to V10 R1.42.0 or V10 R1.34.8 and the management interface is network-accessible to authenticated users.

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 4000 Assistant and Manager to version V10 R1.42.0 or V10 R1.34.8 or later. If immediate patching is not possible, restrict network access to management interfaces to trusted IPs and monitor for suspicious command execution patterns.

Recommended fix High confidence

V10 R1.42.0 or V10 R1.34.8

  1. Identify the current version of Unify Openscape 4000 Assistant and/or Manager installed in the environment
  2. If the version is before V10 R1.42.0 or before V10 R1.34.8, plan for an upgrade
  3. Obtain the fixed version (V10 R1.42.0 or V10 R1.34.8) from official Unify/Atos support channels (networks.unify.com)
  4. Follow standard Unify upgrade procedures for Openscape 4000, ensuring proper backups are taken before the upgrade
  5. After upgrade, verify the version is V10 R1.42.0 or V10 R1.34.8 or later
  6. Validate that the command injection vulnerability is no longer present

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

Fix this in Unify Openscape 4000 Assistant Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35032 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