CVE-2023-45351
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.1, 4000 Assistant V10 R0, 4000 Manager V10 R1 before V10 R1.42.1, and 4000 Manager V10 R0 allow Authenticated Command Injection via AShbr. This is also known as OSFOURK-24039.
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 confidenceAuthenticated command injection vulnerability in Atos Unify OpenScape 4000 Assistant and Manager allows remote attackers to execute arbitrary OS commands via the AShbr component. The vulnerability requires valid authentication but can lead to complete system compromise.
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 installed OpenScape 4000 productLocate and inspect the installed Atos Unify OpenScape 4000 software on the system. Check for either OpenScape 4000 Assistant or OpenScape 4000 Manager installations.Affected if Neither product is installed
-
Verify product version is exactly 10Use the product's built-in version check mechanism, about dialog, or system information panel to determine the installed version number.Affected if Version is not exactly 10
-
Confirm AShbr component is enabledInspect the product configuration or component list to determine whether the AShbr component is present and enabled.Affected if AShbr component is not present or not enabled
-
Check network accessibility of management interfaceReview firewall rules and network configuration to determine if the management interface is exposed to network access.Affected if Management interface is not network-accessible (only local access)
The environment is affected if OpenScape 4000 Assistant or Manager version 10 is installed with the AShbr component enabled and the management 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 · scopedUpgrade to OpenScape 4000 V10 R1.42.1 or later. If immediate patching is not possible, restrict network access to management interfaces and enforce strong authentication credentials.
V10 R1.42.1 or later
- Identify the current installed version of Unify Openscape 4000 Assistant or Manager in your environment
- Obtain the fixed version V10 R1.42.1 from official Atos Unify support channels or the Unify support portal
- Review the official upgrade documentation and release notes for V10 R1.42.1
- Perform a complete backup of the current system configuration
- Apply the upgrade to V10 R1.42.1 following the documented upgrade procedure
- Verify the upgrade was successful and the version displays as V10 R1.42.1 or later
- Test that normal operations and the AShbr functionality work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45351 — 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-45351 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