CVE-2023-35035
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 · uneditedAtos 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-23557.
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 confidenceCommand injection vulnerability in Atos Unify OpenScape 4000 Assistant and Manager (versions V10 R0, V10 R1 before V10 R1.42.0 and V10 R1.34.8) allows authenticated users to execute arbitrary OS commands due to insufficient input validation in the web interface.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Atos Unify OpenScape 4000 is installedCheck system inventory or look for OpenScape 4000 Assistant or Manager software on the systemAffected if OpenScape 4000 Assistant or Manager is present on the system
-
Determine the installed versionAccess the web interface or check installed software version through system administration toolsAffected if Version is V10 R0 or V10 R1 prior to V10 R1.42.0 or V10 R1.34.8
-
Verify web interface is accessibleAttempt to access the OpenScape 4000 web interface via HTTP/HTTPS on the expected management portAffected if Web interface is reachable and responds to authentication requests
-
Confirm authentication is required for the web interfaceCheck if the web login page is presented when accessing the management interfaceAffected if Web interface accepts authenticated user sessions
If OpenScape 4000 Assistant or Manager version V10 R0 or V10 R1 prior to V10 R1.42.0 or V10 R1.34.8 is installed and its web interface is accessible with authentication enabled, the environment is affected by this vulnerability.
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 patches by upgrading to V10 R1.42.0 or V10 R1.34.8 or later as specified in Atos advisory OSFOURK-23557; verify no unauthorized access after patching.
V10 R1.42.0 or V10 R1.34.8
- 1. Identify the currently installed version of Unify Openscape 4000 Assistant or Manager by accessing the admin interface or checking system information
- 2. If running Unify Openscape 4000 Assistant or Manager V10 R0, upgrade to V10 R1.42.0 or later
- 3. If running Unify Openscape 4000 Assistant or Manager V10 R1 versions before V10 R1.42.0, upgrade to V10 R1.42.0 or V10 R1.34.8
- 4. Obtain the upgrade from the official Unify (Atos) support portal at networks.unify.com
- 5. Apply the upgrade following Unify's standard upgrade procedures for the Openscape 4000 platform
- 6. After upgrade, verify the system is functioning correctly and the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35035 — 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-35035 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