CVE-2023-45350
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 Manager V10 R1 before V10 R1.42.1 and 4000 Manager V10 R0 allow Privilege escalation that may lead to the ability of an authenticated attacker to run arbitrary code via AScm. This is also known as OSFOURK-24034.
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 · moderate confidenceAtos Unify OpenScape 4000 Manager contains a privilege escalation vulnerability in the AScm component. An authenticated attacker can exploit this flaw to execute arbitrary code with elevated privileges, potentially achieving full 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= 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.
-
Verify OpenScape 4000 Manager is installedCheck for the presence of OpenScape 4000 Manager in the system inventory or installed programs. Look for directories such as C:\Program Files\Unify\OpenScape 4000 Manager or similar paths.Affected if OpenScape 4000 Manager is found on the system
-
Determine the installed versionLocate the version information in the installation directory, typically in a version.txt, about dialog, or configuration file. Common paths include the installation root directory or within a 'config' subfolder.Affected if The installed version is exactly 10.x (without reaching R1.42.1)
-
Confirm AScm component is accessibleCheck if the AScm web interface or management console is accessible. Verify the AScm service is running and exposed. Look for URLs containing '/ascm' or similar paths in the web server configuration.Affected if AScm component is enabled and network-accessible
-
Review AScm authentication configurationInspect the AScm configuration files or management interface to determine what authentication mechanisms are in place and whether weak or default credentials could be exploited.Affected if AScm uses weak authentication, default credentials, or allows unauthenticated access to privileged functions
-
Check for existing privilege escalation indicatorsReview system logs, AScm access logs, and audit trails for suspicious activity such as unexpected privilege changes, unauthorized administrative actions, or code execution from AScm-related processes.Affected if Logs show unauthorized privilege escalation attempts or successful exploitation attempts targeting AScm
The environment is affected if OpenScape 4000 Manager version 10 is installed with the AScm component accessible to authenticated attackers, particularly if the version has not been updated to V10 R1.42.1 or later.
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 Manager V10 R1.42.1 or later. If immediate patching is not feasible, limit access to AScm to trusted users only and enforce strong authentication mechanisms.
V10 R1.42.1
- Upgrade Unify Openscape 4000 Manager to version V10 R1.42.1 or later to remediate the vulnerability
- Verify the upgrade was successful by checking the software version after installation
- Consult Atos Unify official documentation or support for detailed upgrade procedures specific to your deployment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45350 — 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-45350 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