CVE-2023-30638
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 SBC 10 before 10R3.1.3, OpenScape Branch 10 before 10R3.1.2, and OpenScape BCF 10 before 10R10.7.0 allow remote authenticated admins to inject commands.
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 SBC 10, OpenScape Branch 10, and OpenScape BCF 10 contain a command injection vulnerability that allows remote authenticated administrators to execute arbitrary commands on the underlying system. The vulnerability exists in versions prior to the specified patches (10R3.1.3, 10R3.1.2, and 10R10.7.0 respectively), likely through insufficient input validation in administrative interfaces.
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, < 10r10.7.0>= 10, < 10r3.1.2>= 10, < 10r3.1.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the installed product and versionAccess the administrative interface or use system information commands to determine the exact product name (OpenScape SBC, OpenScape Branch, or OpenScape BCF) and its running version number. This is typically found in the system status or about section of the management console.Affected if The product is OpenScape SBC, Branch, or BCF version 10 running a version lower than 10R3.1.3 for SBC, lower than 10R3.1.2 for Branch, or lower than 10R10.7.0 for BCF.
-
Confirm the product line is within scopeVerify that the installed product matches one of the three affected product lines: OpenScape Session Border Controller, OpenScape Branch, or OpenScape BCF.Affected if The product is any of these three lines and the version is below the fixed releases.
-
Check administrative interface exposureDetermine whether the administrative web interface or management ports are accessible from network locations outside the trusted administrative network.Affected if The admin interface is exposed to untrusted networks, allowing remote authenticated administrators to reach it.
-
Review administrative account accessAudit administrative user accounts and their authentication methods to understand which users have privileged command execution capabilities within the product.Affected if There are administrative accounts configured with the ability to execute system commands through the product interface.
You are affected if you are running any version of Atos Unify OpenScape SBC, Branch, or BCF version 10 that is earlier than the fixed releases (10R3.1.3, 10R3.1.2, or 10R10.7.0 respectively) and the administrative interface is accessible to remote authenticated administrators.
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 · scoped10r3.1.210r3.1.310r10.7.0
Upgrade to Atos Unify OpenScape SBC 10 version 10R3.1.3 or later, OpenScape Branch 10 version 10R3.1.2 or later, and OpenScape BCF 10 version 10R10.7.0 or later. If upgrades cannot be applied immediately, restrict administrative access to trusted IPs only and monitor for suspicious command execution patterns.
OpenScape BCF: 10r10.7.0 or later | OpenScape Branch: 10r3.1.2 or later | OpenScape SBC: 10r3.1.3 or later
- Identify which Unify OpenScape product is in use (BCF, Branch, or SBC)
- Check the current installed version through the admin interface or CLI
- Download the appropriate fixed version from the official Atos Unify support portal (references: networks.unify.com, www.news.de)
- For OpenScape BCF: upgrade to version 10r10.7.0 or later
- For OpenScape Branch: upgrade to version 10r3.1.2 or later
- For OpenScape SBC: upgrade to version 10r3.1.3 or later
- Review and apply any pre-upgrade prerequisites documented in the upgrade guide
- Perform the upgrade following the official upgrade procedure documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30638 — 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-30638 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