dbcve.org
Unify Openscape 4000 AssistantApplication · Atos

CVE-2023-35033

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, Assistant V10 R0, Manager V10 R1 before V10 R1.42.0 and V10 R1.34.8, and Manager V10 R0 allow command injection by authenticated users, aka OSFOURK-23556.

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

This is a command injection vulnerability in Atos Unify OpenScape 4000 Assistant and Manager (V10 R0 and V10 R1). Authenticated users can execute arbitrary OS commands due to improper input validation. The vulnerability affects versions before V10 R1.42.0 and V10 R1.34.8.

MitigationUpgrade to the vendor-provided patched versions (V10 R1.42.0 or V10 R1.34.8 or later) to remediate this command injection vulnerability. Since this is an authenticated command injection, also review and limit user privileges as a defense-in-depth measure.

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 OpenScape 4000 installation
    Locate the Atos Unify OpenScape 4000 Assistant or Manager application on the system. Check the installed program files, or access the management interface login page to confirm the product name.
    Affected if The system has Atos Unify OpenScape 4000 Assistant or Manager installed.
  2. Determine the installed version
    Log into the OpenScape 4000 Manager or Assistant web interface, or check the application's 'About' or 'Version' information panel. Record the exact version number displayed (e.g., V10 R1.x).
    Affected if The exact version number cannot be determined or the product is present.
  3. Compare version against vulnerable ranges
    Compare the installed version number to the known vulnerable versions: any V10 R0.x build or V10 R1.x builds prior to R1.34.8 or R1.42.0.
    Affected if The installed version is V10 R0.x, or V10 R1.x prior to R1.34.8 (if on the R1 branch) or prior to R1.42.0 (if on later branches).
  4. Verify web management interface is accessible
    Confirm that the OpenScape 4000 web management interface (HTTP/HTTPS) is reachable, typically on ports 80, 443, or a configured management port.
    Affected if The management interface is exposed and reachable on the network.
  5. Confirm user authentication is enabled
    Since this is an authenticated command injection, verify whether user accounts exist and authentication is configured for the management interface.
    Affected if User authentication is configured and user accounts can log into the management interface.

A user is affected if Atos Unify OpenScape 4000 Assistant or Manager version 10 is installed and the version is V10 R0.x, V10 R1.x prior to R1.34.8, or V10 R1.x prior to R1.42.0, with the web management interface accessible and user authentication 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 the vendor-provided patched versions (V10 R1.42.0 or V10 R1.34.8 or later) to remediate this command injection vulnerability. Since this is an authenticated command injection, also review and limit user privileges as a defense-in-depth measure.

Recommended fix Moderate confidence

V10 R1.42.0 (or V10 R1.34.8 as alternative)

  1. 1. Identify the current version of Unify Openscape 4000 Assistant or Manager installed
  2. 2. Download the fixed version (V10 R1.42.0 or V10 R1.34.8) from the official Atos Unify support portal or authorized distribution channel
  3. 3. Review the official upgrade documentation for Openscape 4000 before performing the upgrade
  4. 4. Perform the upgrade following the documented procedure
  5. 5. After upgrade, verify the system is running the fixed version (V10 R1.42.0 or later, or V10 R1.34.8)
  6. 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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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